Multiple include errors generated when use cmake-tools as a configuration provider for cpptools

[esynr3z]

Trying to use CMT (cmake-tools) with a CMake simple "hello-world" project.
Project can be configured, built and debugged - no problems here. But it's quite annoying that all includes of standart headers underlined with red squiggly lines:

#include errors detected. Please update your includePath. Squiggles are disabled for this translation unit

cannot open source file "stddef.h" (dependency of "stdio.h")

This happens only if I choose to use cmake-tools as a configuration provider for cpptools. If "none" option is chosen - squiggly lines disappear.

Is it an expected behaviour? I am afraid that if I will chose "none" as a configuration provider, Intellisense will not find all my defines, includes and etc. placed in my CMakeLists.txt. Am I right?

Also I am not sure what is the rigth place for this issue - cpptols repo or cmake-tolls, but decided to start here.

Operating System: Linux Fedora 28
CMake Version: 3.14.4
VSCode Version: 1.38.1
CMake Tools Extension Version: 1.1.3
Cpptools: 0.25.1
Compiler/Toolchain: gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC)

[bobbrow]

This is not expected. We'll need a bit more information though. Can you enable debug logging for the cpptools language server, reload your window, and then share the "custom configuration" sent for your source file? That should let us know what CMake Tools is sending to cpptools.

[esynr3z]

This is what appears in the output pane after I select GCC kit, and perform cmake configure:

Custom configurations received:
  uri: file:///home/esynr3z/MyRepos/c-templates/cmake_simple/src/main.c
  config: {
  "defines": [
    "SUPERDEF"
  ],
  "standard": "c99",
  "includePath": [
    "/home/esynr3z/MyRepos/c-templates/cmake_simple/src"
  ],
  "intelliSenseMode": "clang-x64",
  "compilerPath": "/usr/bin/gcc"
}
Custom browse configuration received: {
  "browsePath": [
    "/home/esynr3z/MyRepos/c-templates/cmake_simple/src"
  ],
  "standard": "c99",
  "compilerPath": "/usr/bin/gcc"
}
cpptools/didChangeCustomConfiguration
terminating child process: 1978
still alive, killing...
not exited yet. Will sleep for 1 seconds and try again
Closing the communication channel.
Shutting down IntelliSense server: /home/esynr3z/MyRepos/c-templates/cmake_simple/src/main.c
Checking for syntax errors: file:///home/esynr3z/MyRepos/c-templates/cmake_simple/src/main.c
cpptools/didChangeCustomBrowseConfiguration
cpptools/resumeParsing
sending compilation args for /home/esynr3z/MyRepos/c-templates/cmake_simple/src/main.c
  include: /home/esynr3z/MyRepos/c-templates/cmake_simple/src
  include: /usr/include/c++/8
  include: /usr/local/include
  include: /usr/include
  define: SUPERDEF
  other: --gcc
  other: --gnu_version=80100
  stdver: c99
  intelliSenseMode: gcc-x64
queue_update_intellisense for files in tu of: /home/esynr3z/MyRepos/c-templates/cmake_simple/src/main.c
errorSquiggles count: 7
Error squiggles will be disabled in: file:///home/esynr3z/MyRepos/c-templates/cmake_simple/src/main.c
Update IntelliSense time (sec): 0.361

main.c:

#include <stdlib.h>
#include <stdio.h>

int main(void)
{
    #ifdef SUPERDEF
        printf("aaa\n");
    #else
        printf("Hello World!\n");
    #endif
    return 0;
}

[esynr3z]

Can problem be here?

...
"intelliSenseMode": "clang-x64",
"compilerPath": "/usr/bin/gcc"
...

Should compiler and InilliSenseMode be the same?

Made some experiments. When I add

include_directories(/usr/lib64/clang/6.0.1/include)

to my CMakeLists.txt - squiggly lines disappear, but I can't build the project.

How to force cmake-tools to sent other intelliSenseMode (e.g. gcc-x64)?
Or, how to pass additional include directories to cpptools, when cmake-tools used as a provider, and not add these includes to CMakeLists.txt at the same time?

[bobbrow]

I don't suspect the missing headers to be related to the intelliSenseMode. IntelliSense uses compilerPath to determine the system include path and defines which tend to be compatible between gcc and clang in most cases. I think this is more of a problem with the includePath that cpptools is discovering.

When you run /usr/bin/gcc -v -E -x c /dev/null, what does gcc print out under #include <...> search starts here:?

[bobbrow]

What I'm getting at is that the system include path that cpptools is reporting looks wrong to me.

  include: /usr/include/c++/8
  include: /usr/local/include
  include: /usr/include

I don't expect a c++ path to be in there when you are compiling C99 code. I expect something more like this (though this is a slightly older compiler):

 /usr/lib/gcc/x86_64-linux-gnu/7/include
 /usr/local/include
 /usr/lib/gcc/x86_64-linux-gnu/7/include-fixed
 /usr/include/x86_64-linux-gnu
 /usr/include

[esynr3z]

When you run /usr/bin/gcc -v -E -x c /dev/null, what does gcc print out under #include <...> search starts here:?

 /usr/lib/gcc/x86_64-redhat-linux/8/include
 /usr/local/include
 /usr/include

[bobbrow]

Yes, that looks better. I'm not sure why cpptools didn't get the right one. But it looks like this bug should be transferred over there for investigation

[bobbrow]

One other thing I didn't notice earlier from the log is that cpptools is changing the intelliSenseMode to gcc, so having CMake Tools send clang doesn't seem to matter.

[astraujums]

I seem to have almost exactly the opposite problem. While using CMake Tools, I get the squiggles if I have no .vscode/settings.json file besides my CMakeLists.txt. I can get rid of squiggles if I add the file and have the following in it:

{
    "C_Cpp.default.configurationProvider": "vector-of-bool.cmake-tools"
}

Attached are two tiny workspaces that show the difference. They also show a nuisance of CMake Tools trying to handle non-CMake folders in a multi-root workspace but that is another issue.

VSCode:
Version: 1.41.1 (user setup)
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362

CMake Tools:
1.3.0-beta

CppTools:
0.26.3

CMake:
3.14.1

Toolchain:
Visual Studio Build Tools 2019, x64

vscode_intellisense_ok.zip
vscode_intellisense_squiggles.zip

[sean-mcmanus]

@astraujums The "configurationProvider" property needs to be set in order for the CMake Tools extension to provide config data, which is "by design". Can you clarify if you still believe you are hitting a bug?