Improved {build.*.platform.path}
vars enumeration.
#2652
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.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
This is a tentative fix for #2616. The original issue provided an experimental platform that extends
esp32
to experiment with.This PR adds the following template variables that will be available to compose recipes:
{build.core.platform.path}
contains the path to the reference (build) platform{build.board.platform.path}
contains the path to the board platformAlso, adds the input variable
build.use_core_platform_for_runtime_platform_path
to be set onboards.txt
orplatform.txt
:true
then the value of{runtime.platform.path}
will be the path to the reference platform.!=true
) the value of{runtime.platform.path}
will be the path to the board platform (as it always has been)What is the current behavior?
The compile fails with an "extended" platforms
What is the new behavior?
Unfortunately, the compile still fails. Hopefully, this PR could help to resolve the remaining issues.
Does this PR introduce a breaking change, and is titled accordingly?
Other information
/cc @egnor