microsoft / microsoft/vscode-cpptools-api
Add support for specifying separate C and C++ compiler paths and args
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Related to: https://github.com/microsoft/vscode-cpptools/issues/9266
Opening this to track updating compilerPath, compilerArgs, and compilerFragments fields to allow separate values to be provided for C vs. C++.
Contributor guide
No contributing guide indexed for this repository
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 reading the related vscode-cpptools issue 9266 and locate the public API definitions for compilerPath, compilerArgs, and compilerFragments. Determine how separate C and C++ values should be represented, then verify that the API supports distinct values for both languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, typescript
- Domain
- compilers, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100