How to set intelliSenseMode when using CMake Kits?

[emptyVoid]

"C_Cpp.default.intelliSenseMode": "clang-x86" setting is ignored in my setup:

[01.02.2022, 11:51:54] For C source files, IntelliSenseMode was changed from "windows-clang-x86" to "windows-msvc-x86" based on compiler args and querying compilerPath: "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe"
[01.02.2022, 11:51:54] For C++ source files, IntelliSenseMode was changed from "windows-clang-x86" to "windows-msvc-x86" based on compiler args and querying compilerPath: "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe"

No idea where this nonsense with x64 and cl.exe comes from since I'm using x86 and clang-cl.exe.

[Sean McManus (sean-mcmanus)]

Do you have a compilerPath, configurationProvider, or compileCommands set in a setting or c_cpp_properties.json?

[emptyVoid]

Did you use the CMake: Select a Kit command to select the clang-cl.exe compiler?

No, I manually created a kit.

  {
    "name": "clang-cl",
    "keep": true,
    "compilers": {
      "C": "C:\\Program Files (x86)\\LLVM\\bin\\clang-cl.exe",
      "CXX": "C:\\Program Files (x86)\\LLVM\\bin\\clang-cl.exe"
    },
    "visualStudio": "3f22bc6d",
    "visualStudioArchitecture": "x86"
  }

If you run the C/C++: Log Diagnostics command and look for "Custom configurations" in the logging you can see what compilerPath is being set by CMake Tools (which in turn will determine the intelliSenseMode that is used).

If you mean "Custom browse configuration", it does have a line: "compilerPath": "c:/program files (x86)/llvm/bin/clang-cl.exe", . Though "Current Configuration" section for some reason have this: "compilerPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\VC\\Tools\\MSVC\\14.16.27023\\bin\\Hostx64\\x64\\cl.exe",.

[Sean McManus (sean-mcmanus)]

Yeah, the issue is caused by CMake Tools sending us a cl.exe compilerPath in the "Current Configuration". I've transfered the issue to vscode-cmake-tools .

[Sean McManus (sean-mcmanus)]

Oh, sorry, I confused "Current Configuration" with "Custom Configuration" -- if you don't see "Custom Configuration" that means CMake Tools isn't sending us configuration info for the current source file for some reason and it's falling back to cl.exe that may be getting picked us as a default, which you could potentially override by setting the compilerPath to the clang-cl one.

[emptyVoid]

Doesn't seem to work. I see a few C/C++ Configuration Warnings:

[04.02.2022, 23:45:49] Unable to resolve configuration with compilerPath "C:\Program Files (x86)\LLVM\bin\clang-cl.exe".  Using "cl.exe" instead.
[04.02.2022, 23:45:50] Unable to resolve configuration with compilerPath "C:\Program Files (x86)\LLVM\bin\clang-cl.exe".  Using "cl.exe" instead.
[04.02.2022, 23:45:51] Unable to resolve configuration with compilerPath "c:/program files (x86)/llvm/bin/clang-cl.exe".  Using "cl.exe" instead.
[04.02.2022, 23:45:54] Unable to resolve configuration with compilerPath "c:/program files (x86)/llvm/bin/clang-cl.exe".  Using "cl.exe" instead.
[04.02.2022, 23:45:54] Unable to resolve configuration with compilerPath "c:/program files (x86)/llvm/bin/clang-cl.exe".  Using "cl.exe" instead.
[04.02.2022, 23:45:54] Unable to resolve configuration with compilerPath "c:/program files (x86)/llvm/bin/clang-cl.exe".  Using "cl.exe" instead.
[04.02.2022, 23:45:55] Unable to resolve configuration with compilerPath "c:/program files (x86)/llvm/bin/clang-cl.exe".  Using "cl.exe" instead.

And the C/C++ Diagnostics has these in Translation Unit Configurations:

Compiler Path: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe
IntelliSense Mode: windows-msvc-x64

Whereas Current Configuration, Custom browse configuration, and Custom configurations have this:

"compilerPath": "C:\\Program Files (x86)\\LLVM\\bin\\clang-cl.exe",

I guess last time I ran C/C++: Log Diagnostics command with non-cpp file active in the editor.

[Bob Brown (bobbrow)]

So it sounds like CMake Tools is sending the correct compiler, but cpptools is having issues with it. I believe cpptools should log the command it's using to query the compiler. Colen Garoutte-Carson (@Colengms) does that go in the configuration warnings output, or the regular C/C++ output with cmake.loggingLevel set to debug?