You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that due to the two-tier nature of the cFE build system (CMake generate step for the mission called within mission_build.cmake), cache variables defined at cmake invokation are not passed on to individual apps. The only variables accessible are the ones written to mission_vars.cache, namely:
For example, we can set -DENABLE_UNIT_TEST and that will be available to use in an app's CMakeLists.txt, but passing -DENABLE_MYAPP_OPTIONAL_TESTS will have no effect, and ENABLE_MY_APP_OPTIONAL_TESTS will not be defined in the CMakeLists.txt
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It seems that due to the two-tier nature of the cFE build system (CMake generate step for the mission called within mission_build.cmake), cache variables defined at
cmake
invokation are not passed on to individual apps. The only variables accessible are the ones written tomission_vars.cache
, namely:For example, we can set
-DENABLE_UNIT_TEST
and that will be available to use in an app'sCMakeLists.txt
, but passing-DENABLE_MYAPP_OPTIONAL_TESTS
will have no effect, andENABLE_MY_APP_OPTIONAL_TESTS
will not be defined in theCMakeLists.txt
Is there any way around this?
Beta Was this translation helpful? Give feedback.
All reactions