Allow a 'paths-relative-to' key in the firmware config #70
Conversation
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
rgantois
requested changes
Jul 24, 2025
… final fw_configs fw_configs will always be a dictionnary, but individual ones might not.
configs paths-relative-to can be CWD, THIS_FILE, or a literal path. It defaults to CWD. The firmware configs will be patched accordingly: binary paths will be prefixed by either the current working directory (this is the old behaviour), the directory containing the firmware config file, or the literal path. Signed-off-by: Félix Piédallu <[email protected]>
Salamandar
force-pushed
the
relative_paths
branch
from
a3804c3 to
0d20174
Compare
This new option of the configuration file indicates that paths to images are relative to a specific path. Signed-off-by: Félix Piédallu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Closes #68
paths-relative-to can be CWD, THIS_FILE, or a literal path. It defaults
to CWD.
The firmware configs will be patched accordingly: binary paths will be
prefixed by either the current working directory (this is the old
behaviour), the directory containing the firmware config file, or the
literal path.
Let me know if you prefer the CWD behaviour to do nothing (like the current behaviour) instead of prefixing with os.getcwd().