WSL Include file not found in include path

[eesaber]

• VSCode Version: 1.12.1
• C/C++Plugin Version: 0.11.0
• OS Version: Windows 10 64-Bit with Creator update
  

Hello, I am a bash on Ubuntu on Windows user. And I've had some problems when I was programming in C++. When I put the headers (includes) then it appeared this: "include file not found in include path". How can I fix this? I try to add "/usr/include" into it as the figure shows.

in c_cpp_properties.json . But it does not works.
Thank you!

[SkyRiderMike]

I meet the same problem also..

VSCode Version: 1.12
OS Version: windows 10 Latest Update
Steps to Reproduce:
set bash Ubuntu on win10 asthe default command window for visual code
add include path for c++ headers on WSL, such as : "C:/Users/user_name/AppData/Local/lxss/rootfs/usr/include/c++/5 " in c_cpp_properties.jason
And this won't work...visual code still can't find these c++ header for linux sub-system.

[JirkaValtr]

I just had a similar issue trying to use VSCode with MinGW on Windows 10 (no Ubuntu on Windows in my case). And I have been able to solve it by adding the include paths to the browse.path property rather than just to the includePath property. So in your case

"browse": { 
    "path": [
        "/usr/include",
        "/usr/local/include"
    ],

It seems to be an inconsistency between the recommended property to edit (includePath) and the one that is being used by IntelliSense by default (browse.path). See the FAQ here for more info (note that the default intelliSenseEngine in the VSCode settings is the Tag Parser).

[zinechant]

@JirkaValtr Thanks for your solution. I am also using VSCode with MinGW on Windows 10. After I added the paths to the browse.path, I found that the C/C++ plugin complains that functions like 'fprintf'. 'fopen' are not defined although I did include <cstdio> or <stdio.h>(I tried both of them, they both don't work). Have you ever encountered the similar situations? Thanks.

VSCode Version: 1.12.2
C/C++Plugin Version: 0.11.1

[JirkaValtr]

I tried to replicate your situation, but the following code ran fine for me, and the C/C++ plugin didn't complain about anything.

#include <cstdio>
#include <cstdlib>

int main() {
    FILE* fo = fopen("myfile.txt","w");
    if (fo != NULL) fclose(fo);
}

[sean-mcmanus]

@zinechant What version of gcc and/or libc++ are you using?

[zinechant]

@JirkaValtr Thanks a lot for your reply. I have no clue why it doesn't work in my situation.
@sean-mcmanus I am using MinGW with g++ V5.3.0. I don't know how to check the libc++ version that MinGW uses. From a quick search, it seems MinGW built against libmsvcrt.a rather than glibc.

[sean-mcmanus]

@zinechant Probably there are more paths you need to add. If you open the #include files to see what squiggles they show, that might help diagnose the problem. I don't think we've tested on WSL yet, so there might be issues.

[bobbrow]

Since you're on Windows, the IntelliSense mode defaults to Microsoft mode, not gcc/clang mode.

We don't expose any controls to switch this right now, but you can see if replacing %userprofile%\.vscode\extensions\ms-vscode.cpptools-0.11.1\bin\msvc.64.intel.json with msvc.64.linux.json fixes it.

[eesaber]

@bobbrow Thanks for your reply. It still not works. Will the control which can switch to gcc mode become a setting option in future release?

[bobbrow]

Yes, it is on our backlog.

[SkyRiderMike]

That's great to hear...i am looking forward windows' version of visual code cpptools will support bash on ubuntu gcc mode

[bobbrow]

@eesaber I had success with the following config:

        {
            "name": "WSL",
            "intelliSenseMode": "clang-x64",
            "includePath": [
                "${workspaceRoot}",
                "${localappdata}/lxss/rootfs/usr/include/c++/5",
                "${localappdata}/lxss/rootfs/usr/include/x86_64-linux-gnu/c++/5",
                "${localappdata}/lxss/rootfs/usr/include/c++/5/backward",
                "${localappdata}/lxss/rootfs/usr/lib/gcc/x86_64-linux-gnu/5/include",
                "${localappdata}/lxss/rootfs/usr/local/include",
                "${localappdata}/lxss/rootfs/usr/lib/gcc/x86_64-linux-gnu/5/include-fixed",
                "${localappdata}/lxss/rootfs/usr/include/x86_64-linux-gnu",
                "${localappdata}/lxss/rootfs/usr/include"
            ],
            "defines": [
                "__linux__",
                "__x86_64__"
            ],
            "browse": {
                "path": [
                    "${localappdata}/lxss/rootfs/usr/include/c++/5",
                    "${localappdata}/lxss/rootfs/usr/include/x86_64-linux-gnu/c++/5",
                    "${localappdata}/lxss/rootfs/usr/lib/gcc/x86_64-linux-gnu/5/include",
                    "${localappdata}/lxss/rootfs/usr/local/include",
                    "${localappdata}/lxss/rootfs/usr/lib/gcc/x86_64-linux-gnu/5/include-fixed",
                    "${localappdata}/lxss/rootfs/usr/include/x86_64-linux-gnu",
                    "${localappdata}/lxss/rootfs/usr/include/*"
                ],
                "limitSymbolsToIncludedHeaders": true,
                "databaseFilename": ""
            }
        }

An option to select clang/gcc mode on Windows is coming in the next update. I have tested it with MinGW on Windows and it works well for me. I will test it with WSL tomorrow. Watch the release notes for instructions. We'll add a FAQ for WSL with this config in it as well, since we're not going to auto-detect it for you right now.