-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Extend build_info.yml #84906
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.
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
Merged
fabiobaltieri
merged 4 commits into
zephyrproject-rtos:main
from
tejlmand:sysbuild/build_info_images
Feb 10, 2025
Merged
Extend build_info.yml #84906
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
26741a5
cmake: store board directories in build_info
tejlmand 1cbd994
cmake: support array of maps in yaml module
tejlmand cbd1b7f
scripts: support list of images in build info
tejlmand 79ac5a8
sysbuild: populate build_info with list of images
tejlmand File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be a LIST?
I have mixed feelings on this. It should have been caught by
yaml_set
as an invalid syntax, but on the other hand, ifVALUE MAP
works on actual values (ie. maps, not map lists) it may offer a way to set multiple fields in one go?Not blocking but looking for feedback / other opinions 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pillo79 thanks for noticing, but the
build_info()
itself only supports VALUE and PATH, where PATH simply indicates that the value(s) should be adjusted to abs path:zephyr/cmake/modules/extensions.cmake
Lines 3700 to 3703 in 0c368e8
The reason for that, is that
build_info()
uses the build_info schema to determine if the actual tag should be passed toyaml_set()
as a list or a value.zephyr/cmake/modules/extensions.cmake
Lines 3759 to 3767 in 0c368e8
That way the caller of
build_info()
doesn't need to consider this detail 😉But this is only something we can do in build info, because we know there is a schema associated with build info.
The generic yaml implementation cannot know such details, and therefore requires the caller to specify this.