Closed julienlavergne closed 3 weeks ago
Passing this to vscode-cpptools because I think this might be an issue in interrogating the compiler.
@sean-mcmanus Could you transfer this bug?
@Colengms could you take a look at this issue? It appears to have been missed.
Hi @julienlavergne . You mentioned that you have set, "C_Cpp.loggingLevel": "Debug"
already. Could you provide the contents of the C/C++
output channel, from startup until opening a file (that should be configurable via CMake Tools)? That should give us some clues as to the source of the compiler path, and whether the warning is interfering with your IntelliSense configurations.
This issue has been closed because it needs more information and has not had recent activity.
Brief Issue Summary
When setting up, the C/C++ extension returns an warning mentionning a non existing
compilerPath
provided by the Cmake Tools extension. The thing is, I do not have that path anywhere visible in my configuration, so I do not know where it comes from.The warning appears in the C/C++ configuration warnings output window, and does not seem to be blocking to get everything working. I am simply not sure if it hides a bigger problem.
In my setup, I have a multiroot workspace. The active project is a CMake project, the others are a mixed bag, some are CMake, some are not. I am running vscode on Windows and ssh on a Linux box. The C/C++ and CMake Tools extension are installed both locally and remotely. I must say, everything works fine except for this strange warning.
Looking at the logs "C/C++", I get this for all the projects in my workspace except the main active one:
For the main active project, I get:
(Besides the fact that I do not understand why CMake Tools is involved in non-CMake projects, or even in CMake project I did not configure.) Note the difference of version in the compiler:
gcc-13.1.0
vsgcc-13.2.0
, and the inclusion ofcompilerArgsLegacy
instead ofcompilerArgs
."gcc-13.1.0" was really installed there at some point in the past, but it's gone now. And there is no reference to "gcc-13.1.0" anywhere in my settings or cmake files. I started with empty build folder in my main project, and I even deleted the whole
.vscode-server
on my Linux remote to make sure it was not keeping some settings in a Cache.I tried to reset the things as much as I could:
but the warning is there each time I open VSCode after the configure is done.
Where does
compilerPath
comes from in theCustom browse configuration
sent from CMake Tools for projects that are not CMake or for projects that are not configured ? Why is CMake even involved at all here ? The compile-commands of my main project is enough to feed intelisense for all the projects in my workspace, and I don't expect there is anything to do for them indiviually.CMake Tools Diagnostics
Debug Log
Additional Information
/home/myhome/workspace/my-main-cmake-project/.vscode/c_cpp_properties.json
/home/myhome/workspace/my-main-cmake-project/.vscode/settings.json
I do not have any CMake settings in my User settings. Only the C/C++
"C_Cpp.loggingLevel": "Debug"