microsoft / microsoft/vscode-cpptools
[Regression] The default path for Compiler path isn't the valid path in the drop-down list but cl.exe
Open
Nobody has claimed this yet.
bug
Language Service
regression
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and Version: Win
- VS Code Version: 1.92.2
- C/C++ Extension Version: 1.22.1(pre-release)
- If using SSH remote, specify OS of remote machine: NA
Bug Summary and Steps to Reproduce
Bug Summary: The default path for Compiler path isn't the valid path in the drop-down list but cl.exe
Steps to reproduce:
- Create a Test folder and open with VS Code.
- Press F1 to open command palette and type 'C/C++: Edit Configurations (UI)'.
- Observe Compiler path.
Actual behavior:
Expected behavior:
More info:
- This is a regression issue; it cannot repro in C++ Extension v1.13.9
- This issue cannot repro on Mac\Linux\MinGW version, only repro no Windows version.
Configuration and Logs
NA
Other Extensions
No response
Additional context
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
Reproduce the Compiler path behavior on Windows with VS Code 1.92.2 and C/C++ Extension 1.22.1, then compare it with extension 1.13.9. Trace the C/C++: Edit Configurations (UI) compiler-path control and its drop-down values; done means the default is a valid listed compiler path on Windows without regressing Mac, Linux, or MinGW behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100