Demo Multi-Target Build System with All Apps in Bundle#874
Draft
Demo Multi-Target Build System with All Apps in Bundle#874
Conversation
Merge remote-tracking branch 'public-github-nasa/main' into techdev-multitarget-bundle
Also updates two new tools submodules to reflect the updated main branch
Contributor
|
Damon mentioned that there might be some issues with MM on this branch. |
Contributor
|
I pulled that MM feature (nasa/MM#99) and tested it with this code. Details |
Contributor
|
the cfs_test_suite passed on cpu2: Details |
Contributor
|
test on cpu1 passed, too: Details |
| | ym | Lower-case abbreviation of the EDS module, typically used in file names | lc | | ||
| | YM | Upper-case abbreaviation of the EDS module, typically used in source code | LC | | ||
|
|
||
| Additionally, any comment in the form of `/* === C code in xyz file for module YM === */` or `<!-- XML code in xyz file for module YM -->` are no be ignored. So are any comments on or about the example variables or values. These comments are here just to help get the context of where the examples are expected to be found or stand in as placeholders for your own actual, and no doubt very thorough, comments. |
Contributor
There was a problem hiding this comment.
"are no be ignored" should be "are not being ignored".
Thanks to Dave McComas for pointing this out
|
|
||
| For libraries, focus on the DataTypeSet section and skip most of the ComponentSet requirements. | ||
|
|
||
| **Reference Files for EDS XML**: When creating your EDS XML definitions, you can reference existing types and assets from: |
Contributor
There was a problem hiding this comment.
Another comment from Dave McComas here:
I think ‘can’ should be a ‘shall’ “When creating your EDS XML definitions, you can reference existing types and assets from:” Creating guidelines for adding mission-specific types may be helpful. I have a handful of Basecamp types I’ve created that may be worth discussing. Why did I create them and where is the best place to define them?
Perhaps instead of a "shall", a "should" would be more appropriate.
| - `config.xml` - Contains mission-specific configuration parameters and constants | ||
| - See [Update EDS Configuration Files](#3-update-eds-configuration-files) for details on config.xml setup | ||
|
|
||
| * All members of the XML should be found in the config directory. If you wander outside those files, you're probably doing it wrong |
Contributor
There was a problem hiding this comment.
Can this line be clarified?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist (Please check before submitting)
Describe the contribution
This PR brings in multiple changes for demonstration and consideration:
As noted in the
README.mdchanges, this new Makefile implements targets with the following format:Where:
<config>represents a pre-configured example target configuration:native_stdnative_edsosaledslibpc686_rtems5gr712_rtems5rpi_vxworks7rpi_linuxqemu_yocto_linux<goal>represents one of the build steps:prepcompileinstallruntestlcovdetaildesignusersguideosalguideimageSee the README for additional details about each
configandgoal.For example:
Testing performed
N/A
Expected behavior changes
N/A