Visual Studio Code: C++ include path

Question

I'm currently using https://marketplace.visualstudio.com/items?itemName=mitaki28.vscode-clang which is great as a nice little tool for accessing member functions.

I am however having one issue with a project I am importing. While the above clang feature works, I am having particular problem with using include directories. My project structure is as follows:

|- src/
   |- main.cpp
|- include/
   |- MyHelper.h
|- CMakeLists.txt

Is there a way to configure my include directories in Visual Studio Code such that in main.cpp I can just do: #include "MyHelper.h" instead of #include "include/MyHelper.h"?

In the editor, it highlights my include statement saying it's unable to find the file. While the editor is not a big deal (my project compiles), the subsequent issue is the vscode-clang plugin does not work because it does not see the file.

Perhaps even have it use the config from my CMakeLists.txt in the editor for necessary includes?

Thanks!

simply, you must generate [c_cpp_properties.json](https://code.visualstudio.com/docs/languages/cpp#_getting-started) — Роман Супик, Mar 07 '17 at 21:36
c_cpp_properties.json does not help the compiler to find include paths — r0n9, May 16 '18 at 00:45

score 31 · Answer 1 · answered May 16 '18 at 00:40

If you are using CMake, VSCode has CMake plugins to help you build the project. So you do not need to modify the settings.json. Just use:

include_directories("${CMAKE_CURRENT_SOURCE_DIR}/include")

Or if there are no other modules used the header files in that folder you could use something like:

target_include_directories(MyHelper, "${CMAKE_CURRENT_SOURCE_DIR}/include")

If you only need the project be built successfully. That is the whole story.

In the case of that, you got some little green zigzag lines under the #include statements hurting your eyes. You need to generate c_cpp_properties.json. It has nothing to do with helping the compiler to build the code but for helping VSCode intellisense to realize the existence of libraries and header files. And again, you are able to leverage the CMake by adding CMake options in the CMakeLists.txt:

add_definitions(-DCMAKE_EXPORT_COMPILE_COMMANDS=ON)

The CMake will generate a file compile_commands.json under your build directory. The VSCode is able to parse the Json file and find the include path based on the content in that file. So what you need to do is just letting VSCode know where is the Json file. You can do that by adding follwing line in the c_cpp_properties.json:

 "configurations": [
        {
            "name": "Mac",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json",
            ...
        }],

Rebuild the project will let the VSCode intellisense find all necessary paths.

[Environment]
Ubuntu: 16.04.3
VSCode: 1.23.1
VSCode plugins: C/C++ 0.17.0, CMAKE 0.0.17, CMakeTools 0.11.1

`add_definitions(-DCMAKE_EXPORT_COMPILE_COMMANDS=ON)` does not work but `cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON` works fine. Also `set( CMAKE_EXPORT_COMPILE_COMMANDS ON )` works. — kyb, Apr 06 '19 at 18:21
Squiggles went away after following instructions above AND ensuring that my settings included "C_Cpp.intelliSenseEngine": "Tag Parser" — D.Deriso, Jul 30 '21 at 21:34
Is there a way to make vscode automatically look for the `compile_commands.json` file in the build directory? — allo, Apr 26 '22 at 10:45
You may need to restart VSCode after modifying c_cpp_properties.json (inserting compileCommands). — JeffRSon, Nov 04 '22 at 16:01

Deftness · Accepted Answer · 2016-11-13T15:01:21.637

6

Okay, this was foolish, but in the event someone uses Visual Studio Code and does not have a trivial project. These instructions are assuming you're using clang compiler:

Open your project directory
Open .vscode/settings.json

Configure the line below inside of the JSON object:

// Compiler options for C++ (e.g. ['-std=c++11'])
"clang.cxxflags": [
    "-I/path/to/my/include/directory" // header files
],

edited Nov 13 '16 at 15:01

answered Mar 21 '16 at 14:25

Deftness

265
1
4
21

1

I've had the same problem on my side, and when I tried your answer, I am getting another error like following: `Failed to parse "d:\Users\orcuny\Dropbox\HeyHoh\.vscode\c_cpp_properties.json": Unexpected token / in JSON at position 66` – Prometheus Jan 19 '17 at 11:02

score 1 · Answer 3 · edited May 17 '20 at 10:41

I don't know if I'm late. I add arg in tasks.json file. In fact, same as first answer, but in vscode, we can do it easier.

In C++, use g++ -g foo.cpp -o foo -I /path/to/include/dir to add headers files.

As we know, in vscode, tasks.json is using to run bash command, but can use some alias like ${fileDirname} for, you know, file dir name:)

Anyway, task.json:

{
    "tasks": [
        {
            "type": "shell",
            "label": "g++ build active file",
            "command": "/usr/bin/g++",
            "args": [
                "-g",
                "${file}",
                "-o",
                "${fileDirname}/out/${fileBasenameNoExtension}",
                "-I",
                "${fileDirname}/../Include/"
            ],
            "options": {
                "cwd": "/usr/bin"
            }
        }
    ],
    "version": "2.0.0"
}

Visual Studio Code: C++ include path

3 Answers3

Linked