Implement generic location for CFE modules #739
Comments
|
Will also take this opportunity to review the existing search paths that aren't really used. |
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jun 12, 2020
Add more hooks for additional flexibility when adding modular code blobs into the build. Three new directives are added: MISSION_CORE_MODULES, for modular components which are direct dependencies of CFE core and/or extend its functionality. MISSION_GLOBAL_APPLIST, for applications/libraries which should be built for every target, as if they were listed in every TGTx_APPLIST setting. MISSION_GLOBAL_STATIC_APPLIST, same as above but for the TGTx_STATIC_APPLIST setting. This also simplifies/reworks the search path to remove some logic that was never really utilized.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jun 16, 2020
This allows users to more easily find (and configure, if they choose) the standard search path for modular code items. Also print the search path as part of the status messages.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jun 26, 2020
Add more hooks for additional flexibility when adding modular code blobs into the build. Three new directives are added: MISSION_CORE_MODULES, for modular components which are direct dependencies of CFE core and/or extend its functionality. MISSION_GLOBAL_APPLIST, for applications/libraries which should be built for every target, as if they were listed in every TGTx_APPLIST setting. MISSION_GLOBAL_STATIC_APPLIST, same as above but for the TGTx_STATIC_APPLIST setting. This also simplifies/reworks the search path to remove some logic that was never really utilized.
astrogeco
pushed a commit
that referenced
this issue
Jul 1, 2020
Add more hooks for additional flexibility when adding modular code blobs into the build. Three new directives are added: MISSION_CORE_MODULES, for modular components which are direct dependencies of CFE core and/or extend its functionality. MISSION_GLOBAL_APPLIST, for applications/libraries which should be built for every target, as if they were listed in every TGTx_APPLIST setting. MISSION_GLOBAL_STATIC_APPLIST, same as above but for the TGTx_STATIC_APPLIST setting. This also simplifies/reworks the search path to remove some logic that was never really utilized.
astrogeco
pushed a commit
that referenced
this issue
Jul 26, 2020
Add more hooks for additional flexibility when adding modular code blobs into the build. Three new directives are added: MISSION_CORE_MODULES, for modular components which are direct dependencies of CFE core and/or extend its functionality. MISSION_GLOBAL_APPLIST, for applications/libraries which should be built for every target, as if they were listed in every TGTx_APPLIST setting. MISSION_GLOBAL_STATIC_APPLIST, same as above but for the TGTx_STATIC_APPLIST setting. This also simplifies/reworks the search path to remove some logic that was never really utilized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
There are a number of new modular add-ons for CFE that should be distributed with CFE core but aren't really part of the "core" proper. Such as:
These modules should be with the CFE core so that users get a sensible baseline when cloning the CFE core repo as the CFE itself depends on/uses them, but these modules can also be replaced with customized versions at the user discretion.
Describe the solution you'd like
Proposal is to introduce a new top level directory
cfe/modulesto hold these items. This needs to be added to the module path and also to provide a "defaults" file that can select the default set(s) of modules to include if the user doesn't override/replace them.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: