CFE needs to provide CMake-based config file for OSAL #652
Labels
Milestone
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 29, 2020
Rather than CFE generating an osconfig.h file directly, it just needs to select file(s) from the defs directory and pass them to OSAL for the config.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 29, 2020
Rather than CFE generating an osconfig.h file directly, it just needs to select file(s) from the defs directory and pass them to OSAL for the config.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 30, 2020
Rather than CFE generating an osconfig.h file directly, it just needs to select file(s) from the defs directory and pass them to OSAL for the config.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
May 4, 2020
Rather than CFE generating an osconfig.h file directly, it just needs to select file(s) from the defs directory and pass them to OSAL for the config.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
May 4, 2020
Rather than CFE generating an osconfig.h file directly, it just needs to select file(s) from the defs directory and pass them to OSAL for the config.
|
@jphickey , I'm trying to override OS_MAX_FILE_NAME, how do I update OS_MAX_FILE_NAME in native_osconfig.cmake? |
|
@jphickey figured it out. have to set OSAL_CONFIG_MAX_FILE_NAME. |
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.
Currently the CFE cmake script generates an
osconfig.hfile for OSAL to compile with.Describe the solution you'd like
After nasa/osal#285 is fixed (PR nasa/osal#427) the CFE will need to pass OSAL a configuration file in CMake syntax, which then OSAL uses to generate its own
osconfig.h.Additional context
Needed for compatibility
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: