Add commands to get preset names #2433
Merged
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
benmcmorran
commented
Mar 17, 2022
elahehrashedi
approved these changes
Mar 31, 2022
|
@benmcmorran there has been some renaming recently, can you apply it to your branch so that the builds pass, they are failing currently. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This changes commands for command substitution and associated documentation.
The following changes are proposed:
3 new commands:
cmake.activeConfigurePresetName,cmake.activeBuildPresetName,cmake.activeTestPresetName. Each returns a string with the name of the corresponding preset, or an empty string if the preset is not available.The purpose of this change
These commands are designed to be used with the command substitution syntax in
launch.jsonortasks.json. They help to write generic launch configurations or tasks in the presence of CMake projects with multiple presets that may use the${presetName}macro to select thebinaryDir. While the existingcmake.launchTargetPathcan often also be used in this situation, it can't handle constructing the path to files that aren't the target (e.g. associated debug information or, for embedded applications, hex or bin files).FYI @aleun @gcampbell-msft