Vscode-cpptools: Can't easily see or specify `clang` executable (or C++ version) used for Intellisense

Created on 4 Mar 2018  Â·  2Comments  Â·  Source: microsoft/vscode-cpptools

I'm suspecting that the intellisense engine doesn't actually make use of any external executable for parsing or linting, but found no literature to confirm this.

If that is not the case, how do we change the command line arguments passed to the executable (for example to tell it to force a specific C++ std)?

Feature Request Language Service duplicate fixed (release pending)

Most helpful comment

In the March update you will be able to specify your stdver in c_cpp_properties.json. For now we auto-select c++17 (which is not fully implemented yet, but has many of the features available now).

All 2 comments

In the March update you will be able to specify your stdver in c_cpp_properties.json. For now we auto-select c++17 (which is not fully implemented yet, but has many of the features available now).

Please try out https://github.com/Microsoft/vscode-cpptools/releases/tag/v0.16.0-insiders and let us know if there are any issues we should fix before our final release next week.

We improved our ability to guess the clang compiler on Linux OS's if it exists. The compilerPath should show the version we guess, so let us know if you think our guess can be improved or if there's any problems with changing the compilerPath or cppStandard version if you need to do that.

Was this page helpful?
0 / 5 - 0 ratings