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
At build put the response from git describe --tags --always --dirty (similar to version.cmake in cfe/cmake) into a define and report by the code if defined in addition to the manual version number.
Can do it at build -D_ENHANCED_V_NAME_=response from git, or generate a header file on the fly and poke in the #define, and include from the code.
cFS app guide will eventually say something like this, it's the direction we are going with version reporting to eliminate all the manual changes to the version header (only required at release with this update), or the confusion it causes when it's not updated. Since before every merge to master really was a new version but not tracked well.
The text was updated successfully, but these errors were encountered:
At build put the response from
git describe --tags --always --dirty
(similar to version.cmake in cfe/cmake) into a define and report by the code if defined in addition to the manual version number.Can do it at build -D_ENHANCED_V_NAME_=response from git, or generate a header file on the fly and poke in the #define, and include from the code.
cFS app guide will eventually say something like this, it's the direction we are going with version reporting to eliminate all the manual changes to the version header (only required at release with this update), or the confusion it causes when it's not updated. Since before every merge to master really was a new version but not tracked well.
The text was updated successfully, but these errors were encountered: