Andreea Isac

Thank you for helping us fix this by providing a repro. Ideally you wouldn't use compile_commands.json, but CMake Tools provider.

I didn't try to reproduce this again this week but in general, we never saw this, it would help if you can send us a repro, maybe some special situation...

@grigorig , @Torgee , do you happen to reproduce this on a project that is already open source or which can be easily shared on GitHub? It would help us...

@bhspyder, interesting. For IntelliSense, we invoke make with any flags/targets you specify in .vscode/settings.json, plus the following: --dry-run --always-make --keep-going --print-directory. Try to add those and see if you reproduce...

@Colengms, does this ring any bells from the CppTools issues collection?

Fix is merged in and should be included in the 1.15 release.

Thank you for opening this report. You can specify this in the preset as well. I just verified that it works. "cacheVariables": { "CMAKE_EXPORT_COMPILE_COMMANDS": "ON" } @xisui-MSFT, I don't see...

@hwmaier, the same as many other settings that for now, by design, are not automatically inherited from a global settings scope (the one used for variants/kits), "cmake.configureEnvironment" would not be...

@GavinRay97, without the code you reference (about checking clang-cl to be inside the Visual Studio installation path), the extension would always find the same first clang* toolset in the path...

Thank you for opening this issue. We understand this experience can be improved. Also, one question: you got the "no cache object found" error even if you didn't delete the...