microsoft / microsoft/vscode-cmake-tools
Make missing CMake easier to diagnose
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
When cmake.exe is not on path, the error message makes it hard to figure out initially.
Running the "Delete Cache and Reconfigure" command actually shows the root cause - the pop-up on the bottom says "make sure it is installed". I think there should be this pop-up without having to run the "Delete Cache" command, instead of "spawn cmake ENOENT".
### 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 a missing cmake.exe on PATH through the normal configure flow. Compare its error handling with the "Delete Cache and Reconfigure" command, which already shows the clearer installation message. Done means the normal flow displays an actionable popup instead of "spawn cmake ENOENT".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100