My vscode cannot recognize "cout" "endl" etc... (MinGW)

[roblourens]

From @LiuZHolmes on May 23, 2017 3:11

• VSCode Version: Code 1.12.2 (19222cdc84ce72202478ba1cec5cb557b71163de, 2017-05-10T13:20:36.315Z)
• OS Version: Windows_NT ia32 10.0.14393
• Extensions:

Extension	Author	Version
code-gnu-global	austin	0.2.2
code-runner	formulahendry	0.6.17
vscode-clang	mitaki28	0.2.2
cpptools	ms-vscode	0.11.1
debug	webfreak	0.19.0
c-cpp-snippets	wlhe	0.1.0

I already set my cpp_properties correctly(I think),like:

        {
            "name": "Win32",
            "includePath": [ "C:/MinGW/include/*", 
            "C:/MinGW/lib/gcc/mingw32/5.3.0/include/*" ,
            "C:/MinGW/lib/gcc/mingw32/5.3.0/include/c++/*", 
            "C:/MinGW/lib/gcc/mingw32/5.3.0/include/c++/mingw32", 
            "C:/MinGW/lib/gcc/mingw32/5.3.0/include/c++/backward" ],
            "defines": [
                "_DEBUG",
                "UNICODE"
            ],
            "browse": {
                "path": [],
                "limitSymbolsToIncludedHeaders": true,
                "databaseFilename": ""
            }
        }

And with the simple code:

#include <iostream>
using namespace std;
int main(int argc, char const *argv[])
{
	cout << "Hello world!" << endl;
	int a;
	cin >> a;
	return 0;
}

there are errors like:

'identifier "cout" is undefined'
'argument list for variable template "endl" is missing'
'identifier "cin" is undefined'

---

Steps to Reproduce:

1.Install vscode and cpp extensions

2.Set your cpp_properties like me(you may need to change the directory of mingw)

Copied from original issue: microsoft/vscode#27110

[LiuZHolmes]

What's more, if you change your intellisense engine to "Tag Parser", the error also changes to that it can't recognize header iostream. By the way, even in the situation like this I can still build and run my cpp file.

[bobbrow]

If you are using the "Tag Parser" setting, you need to make sure that the browse.path setting is populated. In your c_cpp_properties.json that you shared, it looks like it is empty. You should add

"C:/MinGW/include", 
"C:/MinGW/lib/gcc/mingw32/5.3.0/include"

or similar to your browse.path array. These paths are recursively searched, so use /* if you want to make it non-recursive.

[bobbrow]

And the reason that the new IntelliSense didn't work for you is because on Windows the IntelliSense engine compiles the code in Microsoft mode instead of clang/gcc mode. We don't currently expose a setting to change the mode, but there is a workaround I just tested that resolves the squiggles. It requires you to copy %userprofile%\.vscode\extensions\ms-vscode.cpptools-0.11.1\bin\msvc.64.linux.json over msvc.64.intel.json in the same folder. The Linux JSON file sets the IntelliSense engine to use clang mode instead of Microsoft mode.

[LiuZHolmes]

I tried the second way and it works! And I think the first method can solve it, too. Thanks for your patient explanation.

[LiuZHolmes]

Back again, the error shows up once more after I added another head file below iostream. Then I copied some of my IncludePath to browse.path array. It's OK so far, hope that I've solved it once and for all.

[bobbrow]

Is everything working for you now? If so, you may close this issue. Otherwise, please let me know if there is something else not working and I can help you resolve it.

Thanks.

[igorPhelype]

Same problem here...
What should i do that may solve this problem?

{
    "name": "Linux",
    "includePath": [
        "${workspaceRoot}",
        "/usr/include/c++/5",
        "/usr/local/include",
        "/usr/include"
    ],
    "defines": [],
    "browse": {
        "path": [
            "/usr/include/c++/5",
            "/usr/local/include",
            "/usr/include"
        ],
        "limitSymbolsToIncludedHeaders": true,
        "databaseFilename": ""
    }
}

Thanks for the help 😄

[bobbrow]

@igorPhelype, this issue is about MinGW on Windows. Your configuration looks like standard Linux. Can you please open a new issue and provide some detail about your distro and what exactly is not working for you?

Thanks.

[igorPhelype]

Here's my issue: #765