8000 `WorkspaceBrowseConfiguration` should support multiple sets of compiler path/args · Issue #56 · microsoft/vscode-cpptools-api · GitHub
[go: up one dir, main page]
Skip to content

WorkspaceBrowseConfiguration should support multiple sets of compiler path/args #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Colengms opened this issue May 1, 2024 · 0 comments
Open

WorkspaceBrowseConfiguration should support multiple sets of compiler path/args #56

Colengms opened this issue May 1, 2024 · 0 comments

Comments

@Colengms
Copy link
Contributor
Colengms commented May 1, 2024

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Colengms
0