microsoft / microsoft/vscode-cmake-tools
CMake toolchain files are not indexed/recognized by the extension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
I'm assuming this issue belongs here, based upon the `[Unspecified]` option in the drop-down menu.
> `[Unspecified] Unspecified (Let CMake guess what compilers and environment to use)`
**Expected Behavior:**
I don't care to see this drop-down menu when I have a toolchain file specified in my repository.
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 issue in a VS Code project that specifies a CMake toolchain file, then trace how toolchain files are indexed and how the configuration drop-down is populated. Done means the extension recognizes the specified toolchain and does not show the [Unspecified] option when it is unnecessary; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100