Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update startup processing to optionally use module suffix #981

Closed
skliper opened this issue Oct 29, 2020 · 0 comments · Fixed by #1156
Closed

Update startup processing to optionally use module suffix #981

skliper opened this issue Oct 29, 2020 · 0 comments · Fixed by #1156
Assignees
@jphickey
Labels
enhancement
Milestone
Caelum

Comments

@skliper
Copy link
Contributor

skliper commented Oct 29, 2020

Is your feature request related to a problem? Please describe.
Startup scripts currently need to be modified across systems that have different module suffixes.

Describe the solution you'd like
#941 makes the module suffix available in software. If there is no suffix specified in the startup script, append it (backwards compatible). This would make startup scripts more portable.

Describe alternatives you've considered
None

Additional context
#583 - table implementation would also benefit from not needing the suffix

Requester Info
Jacob Hageman - NASA/GSFC
@skliper skliper added this to the 7.0.0 milestone Jan 22, 2021
jphickey added a commit to jphickey/cFE that referenced this issue Feb 5, 2021
@jphickey
Fix nasa#981, implement better filename parser routine
0881336 
Implmements a new function in FS to parse an input file name
from a user.  Initially applied to startup script processing.

The new function produces fully-qualified output where the input
may omit either a pathname or an extension.  These items will be
added from the specified defaults, if missing, and a complete
fully-qualified filename will be output.

If the input is already a fully qualified filename, then the
output is the same as the input (basically a copy).

This initially is used to provide better cross-platform startup
script processing, where module suffix may differ across platforms.
Only the "basename" of the filename needs to be specified in the
startup script - everything else can come from defaults.
jphickey added a commit to jphickey/cFE that referenced this issue Feb 5, 2021
@jphickey
Fix nasa#981, implement better filename parser routine
cc5c968 
Implmements a new function in FS to parse an input file name
from a user.  Initially applied to startup script processing.

The new function produces fully-qualified output where the input
may omit either a pathname or an extension.  These items will be
added from the specified defaults, if missing, and a complete
fully-qualified filename will be output.

If the input is already a fully qualified filename, then the
output is the same as the input (basically a copy).

This initially is used to provide better cross-platform startup
script processing, where module suffix may differ across platforms.
Only the "basename" of the filename needs to be specified in the
startup script - everything else can come from defaults.
This was referenced Feb 5, 2021
Merged
Closed
astrogeco added a commit that referenced this issue Mar 2, 2021
@astrogeco
Merge pull request #1156 from jphickey/fix-981-better-filename-parser
f55cc82 
Fix #981, implement better filename parser
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jphickey jphickey

Labels
enhancement
Projects
None yet
Milestone
Caelum
Development

Successfully merging a pull request may close this issue.

Fix #981, implement better filename parser jphickey/cFE
2 participants
@jphickey @skliper