microsoft / microsoft/vscode-cmake-tools
CMake's parallel option not respected when using a build preset
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### Brief Issue Summary
I'm getting into the world of build presets, and found that my VSCode configuration - such as the number of parallel builds - is not respected when using a specific build preset.
I'd like it very much to still be respected and take precedence over any presets. I'm aware user presets are an option in cmake, but unless you're going to be stashing and popping them all the time, it is just not practical to store user configuration in the repo code.
As a workaround, using the 'default' build preset is respecting the option so that is nice!
### CMake Tools Diagnostics
_No response_
### Debug Log
_No response_
### Additional Information
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with the VS Code parallel-build configuration and a non-default CMake build preset, comparing it with the default preset workaround. Trace how build presets and the parallel-build option are combined. Done means the VS Code setting is respected and takes precedence when any build preset is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript, vscode
- Domain
- build-system, developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100