microsoft / microsoft/vscode-cmake-tools
Automatically configure when switching kits
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
When switching kits, it's necessary to also run Configure to configure with the kit. Perhaps switching kits should automatically trigger configuration? Or, short of that, perhaps add a setting to enable configuration when switching kits. There is an existing setting to auto configure on open. These could be merged, so CMake is always maintained in a configured state. Though, even when not (re-)configuring on open, it would seem beneficial to always configure when switching kits.
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 tracing the kit-switching flow and the existing auto-configure-on-open setting in the TypeScript extension. Determine how configuration is invoked in each case; done means switching kits reliably leaves CMake configured, with the related behavior covered by the project's existing tests if available.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100