chore: add vscode cmake configuration #3008
Merged
Conversation
This file contains 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
This sets the build directory to `build/release` for the extension documented at https://vector-of-bool.github.io/docs/vscode-cmake-tools/settings.html#cmake-builddirectory. It also sets the generator to `make`, since otherwise it tries `Ninja` which doesn't work.
eric-wieser
changed the title
|
awaiting-review |
github-actions
bot
added
awaiting-review
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 sets the build directory to
build/releasefor the "CMake Tools for Visual Studio Code" extension documented at https://vector-of-bool.github.io/docs/vscode-cmake-tools/settings.html#cmake-builddirectory.It also sets the generator to
make, since otherwise it triesNinjawhich doesn't work.Without these settings, the extension runs configure in a bad place at startup.
This does not add the cmake tools extension to the default workspace configuration; the goal is simply to prevent bad behavior for users who already have the extension enabled.
Summary
Screenshot of this in action:
Link to
RFCorbugissue: N/A, this is not a bug nor a user-visible feature.