CMake optimization #533
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#533
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "mueller/cmake-optimization"
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?
If the uppermost
CMakeLists.txt
does not have the include paths set up properly, there can be compile errors that#include "fsfw/FSFW.h"
was not found. This should fix the issue.From what I have seen, the additional target include directories are obsolete because there is nothing of interest inside the
fsfw/src
binary directory.The configure file will be copied to the
fsfw
folder of the build directory and then is accessible inside thefsfw/
header namespace forthe FSFW. They are a little bit private in that sense, but the user can still access the FSFW version as a side effect if they include the upper most binary directory in CMake, but a cleaner way would be to define a function somewhere to access the version defines. Maybe something like a
getVersion
function inside aversion.cpp
/version.h
which simply returns the version integers.I like the idea of a
getVersion
. Sounds useful.