`WorkspaceBrowseConfiguration` should support multiple sets of compiler path/args
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake, cpp, typescript
Research direction
Start by reading the WorkspaceBrowseConfiguration API and reviewing how cpptools processes compile_commands.json, as described in the issue. Define and document support for multiple compiler path/argument sets, including distinct C and C++ queries; done means the API can represent these sets for subprojects without requiring redundant compiler queries.
Written by the indexing model from the issue text.
Description
If I understand correctly, it’s not uncommon for CMake projects to consist of several subprojects that could use different relevant args or hypothetically even different compilers (i.e. target binaries vs. tools built for the host system to be used by the build).
There is also the need for C vs. C++ information, as compiler queries for either may result in different system include paths.
Processing N sets of compiler paths/args here would be similar to what cpptools does with compile_commands.json files - processes all provided compiler paths and (unique and relevant combinations of) args, to build the browse path(s). Cpptools should be able to avoid redundantly querying compilers, so it should not be critical that the configuration provider de-dupe this set.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
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.
More from microsoft/vscode-cpptools-api
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/vscode-cpptools-api#50 · 2 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/vscode-cpptools-api#43 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/vscode-cpptools-api#42 · 2 comments · 1 reaction ·
All issues in microsoft/vscode-cpptools-api
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·