Обнаружены ошибки include измените includepath

The answer is here: How to use C/Cpp extension and add includepath to configurations.

Click the light bulb and then edit the JSON file which is opened. Choose the right block corresponding to your platform (there are Mac, Linux, Win32 – ms-vscode.cpptools version: 3). Update paths in includePath (matters if you compile with VS Code) or browse.paths (matters if you navigate with VS Code) or both.

Thanks to @Francesco Borzì, I will append his answer here:

You have to Left 🖰 click on the bulb next to the squiggled code line.

If a #include file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.

answered Aug 9, 2017 at 6:51

If you are working with cmake-tools and the error messages says something is wrong with the configurationProvider, then you have 2 options:

1. Use ms-vscode.cpptools instead of ms-vscode.cmake-tools
2. Define the headers in CMakeLists.txt

Option 1: Use ms-vscode.cpptools instead of ms-vscode.cmake-tools.

1. Open c_cpp_properties.json. (windows key on windows or cmd key on mac + shift + p, enter «c/c++ edit configurations» and chose ‘json’.
2. Enter ms-vscode.cpptools as value for configurationProvider instead of ms-vscode.cmake-tools or whatever you have.

How it should look like after the replacement of configurationProvider:

One other important configuration is the include path. The assumption is that you have this configuration right. May be like following

Option 2: Define the headers in CMakeLists.txt

When configurationProvider is set to ms-vscode.cmake-tools in c_cpp_properties.json, VS Code uses the include information defined in the CMakeLists.txt instead of reading the includePath configs in VS Code.

So you need to setup the include path correctly:

1. using the include_directories command (rather than the target_include_directories command) to define the headers
2. Configure the project to reflect the change happened in the previous step.

• Left mouse click on the bulb of error line
• Click Edit Include path
• Then this window popup

• Just set Compiler path

answered May 31, 2020 at 6:51

I ended up here after struggling for a while, but actually what I was missing was just:

If a #include file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.

source: https://code.visualstudio.com/docs/languages/cpp#_intellisense

answered Jan 8, 2019 at 22:14

I’m on a Macbook M1 Pro, and I had red squiggly error lines all over my C++ files. To solve, I did this:

1. Open Preferences -> Settings
2. Search for intelliSenseEngine
3. Change «C_Cpp: Intelli Sense Engine» from Default to Tag Parser

alternatively, you could create a .vscode folder in your project root, and then create a settings.json with the content of

{
    "C_Cpp.intelliSenseEngine" : "Tag Parser"
}

ideally, you should have a c_cpp_properties.json file in the same folder with the right settings as well.

Note: I got this idea from Github here.

answered Aug 31, 2019 at 23:18

I was trying a hello world program, and this line:

#include <stdio.h>

was underlined green. I tried:

1. Deleting the line
2. Re-writing the line
3. Clicking the yellow bulb and choosing to update

fixed the error warning. i don’t know if it fixed the actual problem. But then i’m compiling via a linux VM on Windows 10

answered Sep 20, 2017 at 12:14

Go to your c_cpp_properties.json file by searching from settings.There you might see the following code

{
    "configurations": [
        {
            "name": "Linux",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [],
            "compilerPath": "/usr/bin/gcc",
            "cStandard": "gnu17",
            "cppStandard": "c++17",
            "intelliSenseMode": "linux-gcc-x64"
        }
    ],
    "version": 4
}

Change the compiler path as below

"compilerPath": "/usr/bin/g++",

answered Mar 7, 2021 at 19:10

PatrickPatrick

1191 silver badge3 bronze badges

PickiPicki

4694 silver badges11 bronze badges

navinrangarnavinrangar

92410 silver badges21 bronze badges

answered Dec 2, 2022 at 17:29

My header file was in include/head.h, code in src/code.cpp. I wrote

#include "head.h"

and got this error. Changing it to

#include "../include/head.h"

fixed it.

answered Mar 16, 2022 at 22:06

answered Apr 4, 2020 at 8:30

In case you’ve copied and pasted code into your new file in VS Code

Please delete #include <iostream> and try to build again.

The answer is here: How to use C/Cpp extension and add includepath to configurations.

Click the light bulb and then edit the JSON file which is opened. Choose the right block corresponding to your platform (there are Mac, Linux, Win32 – ms-vscode.cpptools version: 3). Update paths in includePath (matters if you compile with VS Code) or browse.paths (matters if you navigate with VS Code) or both.

Thanks to @Francesco Borzì, I will append his answer here:

You have to Left 🖰 click on the bulb next to the squiggled code line.

If a #include file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.

answered Aug 9, 2017 at 6:51

If you are working with cmake-tools and the error messages says something is wrong with the configurationProvider, then you have 2 options:

1. Use ms-vscode.cpptools instead of ms-vscode.cmake-tools
2. Define the headers in CMakeLists.txt

Option 1: Use ms-vscode.cpptools instead of ms-vscode.cmake-tools.

1. Open c_cpp_properties.json. (windows key on windows or cmd key on mac + shift + p, enter «c/c++ edit configurations» and chose ‘json’.
2. Enter ms-vscode.cpptools as value for configurationProvider instead of ms-vscode.cmake-tools or whatever you have.

How it should look like after the replacement of configurationProvider:

One other important configuration is the include path. The assumption is that you have this configuration right. May be like following

Option 2: Define the headers in CMakeLists.txt

When configurationProvider is set to ms-vscode.cmake-tools in c_cpp_properties.json, VS Code uses the include information defined in the CMakeLists.txt instead of reading the includePath configs in VS Code.

So you need to setup the include path correctly:

1. using the include_directories command (rather than the target_include_directories command) to define the headers
2. Configure the project to reflect the change happened in the previous step.

• Left mouse click on the bulb of error line
• Click Edit Include path
• Then this window popup

• Just set Compiler path

answered May 31, 2020 at 6:51

I ended up here after struggling for a while, but actually what I was missing was just:

If a #include file or one of its dependencies cannot be found, you can also click on the red squiggles under the include statements to view suggestions for how to update your configuration.

source: https://code.visualstudio.com/docs/languages/cpp#_intellisense

answered Jan 8, 2019 at 22:14

I’m on a Macbook M1 Pro, and I had red squiggly error lines all over my C++ files. To solve, I did this:

1. Open Preferences -> Settings
2. Search for intelliSenseEngine
3. Change «C_Cpp: Intelli Sense Engine» from Default to Tag Parser

alternatively, you could create a .vscode folder in your project root, and then create a settings.json with the content of

{
    "C_Cpp.intelliSenseEngine" : "Tag Parser"
}

ideally, you should have a c_cpp_properties.json file in the same folder with the right settings as well.

Note: I got this idea from Github here.

answered Aug 31, 2019 at 23:18

I was trying a hello world program, and this line:

#include <stdio.h>

was underlined green. I tried:

1. Deleting the line
2. Re-writing the line
3. Clicking the yellow bulb and choosing to update

fixed the error warning. i don’t know if it fixed the actual problem. But then i’m compiling via a linux VM on Windows 10

answered Sep 20, 2017 at 12:14

Go to your c_cpp_properties.json file by searching from settings.There you might see the following code

{
    "configurations": [
        {
            "name": "Linux",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [],
            "compilerPath": "/usr/bin/gcc",
            "cStandard": "gnu17",
            "cppStandard": "c++17",
            "intelliSenseMode": "linux-gcc-x64"
        }
    ],
    "version": 4
}

Change the compiler path as below

"compilerPath": "/usr/bin/g++",

answered Mar 7, 2021 at 19:10

PatrickPatrick

1191 silver badge3 bronze badges

PickiPicki

4694 silver badges11 bronze badges

navinrangarnavinrangar

92410 silver badges21 bronze badges

answered Dec 2, 2022 at 17:29

My header file was in include/head.h, code in src/code.cpp. I wrote

#include "head.h"

and got this error. Changing it to

#include "../include/head.h"

fixed it.

answered Mar 16, 2022 at 22:06

answered Apr 4, 2020 at 8:30

In case you’ve copied and pasted code into your new file in VS Code

Please delete #include <iostream> and try to build again.