Add specifier to generated tool property keys #4795
Closed
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.
By doing so, runtime variable are resolved by using the board specific tools
real life example:
runtime.tools.sketchUploader.path
gets the value of the last one processedwith this PR
runtime.tools.sketchUploader.path.Intel.arc32
andruntime.tools.sketchUploader.path.Intel.i586
get createdwhen resolving
{runtime.tools.sketchUploader}
, the routine searches for a keyruntime.tools.sketchUploader.Vendor.Architecture
If found, the value is obtained by
{runtime.tools.sketchUploader.Vendor.Architecture}.getKey()
, which always contains the required value.If no value is found, the old method is applied