Skip to content
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.

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

c11 is being used instead of gnu17 #1477

Closed
sean-mcmanus opened this issue Oct 8, 2020 · 2 comments · Fixed by #1696
Closed

c11 is being used instead of gnu17 #1477

sean-mcmanus opened this issue Oct 8, 2020 · 2 comments · Fixed by #1696
Assignees
Labels
Milestone

Comments

@sean-mcmanus
Copy link
Contributor

See the repro at microsoft/vscode-cpptools#6279 .

@andreeis
Copy link
Contributor

Possibly related #1489.

@Colengms
Copy link
Contributor

This issue is due to falling back to a hard-coded default, and not querying the compiler to determine what its default actually is. To avoid requiring all config providers from having to do this, we've made a change to the cpptools-api to allow IntelliSenseMode, cStandard and cppStandard to be omitted, and automatically determined by cpptools based on the compilerPath and compilerArgs. I think we have some other changes we'd like make to the API before publishing a new version. Once a new version of cpptools-api is published, CMake Tools can be updated to omit these fields.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants