Open cmaglie opened 1 week ago
Attention: Patch coverage is 40.00000%
with 3 lines
in your changes missing coverage. Please review.
Project coverage is 70.22%. Comparing base (
850f22a
) to head (7af9663
).
Files | Patch % | Lines |
---|---|---|
...al/arduino/cores/packagemanager/package_manager.go | 40.00% | 2 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
(kibitz: build.use_core_platform_for_runtime_platform_path
might not be quite right, since it doesn't just affect the build but in fact just about any variable, including upload and so on?)
Please check if the PR fulfills these requirements
See how to contribute
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