![]() ![]() You helped a lot understanding how it all hang toghether. Thanks a lot for the support and the many suggestion given. I uninstalled clang and now all my problems on Debian are solved. Then, by comparing the configuration logs, and trying to make them match with each other, I removed a few setting and realized that my Debian defaults to a clang compiler (not gcc which is the default for the other machine) and that I had a clang installation on Debian. Now, I wrote my test.cpp with the "concept" declaration and c++20 standard for Intellisense: on this machine it all worked fine. The C++ extension was the same version on the two machines, while VS on OpenSuse was a few main versions behind (but this was not the problem). Opensuse tends to have old versions, so my gcc was still v7, but I upgraded from source to v10.4, in line with my Debian laptop. I have another Linux box with OpenSuse 15.4. It was very insidious, and this is the story on how I got it solved: Wow! I have finally resolved the problem. ![]() Number of files discovered (not excluded): 20836 Preserve breakpoint IDs in workspace state Issue 182541 microsoft/vscode GitHub. home/gualtiero/proj/Cpp/cpp_features/src/concepts.cpp "/home/gualtiero/proj/Cpp/cpp_features/src" "/home/gualtiero/proj/Cpp/cpp_features/build/CMakeFiles", "configurationProvider": "ms-vscode.cmake-tools", "compilerPathInCppPropertiesJson": "/usr/bin/clang", "/home/gualtiero/proj/Cpp/cpp_features/ " However, apart from date, time and process id, the C++ log diagnostic is basically the same. They are not displayed only when the folder is loaded on start-up. Today it seems that the error squiggles stay there also after a "Reload windows". ![]()
0 Comments
Leave a Reply. |