microsoft / microsoft/vscode-cmake-tools
Default CMake Preset Setting in Workspace Settings
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### Brief Issue Summary
Issue: When using multiple workspaces in the same directory, Visual Studio Code's CMake Tools extension does not remember individual CMake presets for each workspace. This leads to the inconvenience of frequently having to manually select the correct preset for each workspace.
Proposed Solution: Introduce a new setting, cmake.defaultConfigurePreset, in the workspace settings. This setting would allow users to specify a default CMake preset for each workspace.
Expected Benefit: This feature would automatically configure each workspace with its specified preset upon opening, simplifying the workflow and reducing manual configuration.
### CMake Tools Diagnostics
_No response_
### Debug Log
_No response_
### Additional Information
_No response_
Contributor guide
Research direction
Review the extension's existing workspace settings and CMake preset selection flow first. Add the proposed cmake.defaultConfigurePreset setting so each workspace can retain and apply its selected preset when opened, then verify behavior with multiple workspaces sharing one directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100