Implement modern CMake packaging #429
Modern CMake packaging requires providing a
XYZconfig.cmake file and then expecting the application code to use
find_package(FSFW REQUIRED). This could be used to configure the FSFW in addition or instead of the
FSFWConfig.h file. It would also allow the user to only compile specific parts of the code through linked targets, e.g. if a user needs the data link layer, they would need to links against the
FSFW::DataLinkLayer and if the user needs RMAP, they would need to link against
FSFW::RMAP. It probably also would be a good idea to restructure the code into modules which are always required (internally) by the FSFW, e.g. returnvalues or the ObjectManager, and components which are optional. If this is done which is an API change anyway, it might also be a good idea to separate sources and headers like it is done in most C++/C projects ( but im not sure about that.. I actually like the current structure)
It probably would be a good idea to move the version management to
CMake completely like suggested in the CMake tutorial
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?