VS Code多根项目能否引用其他根的includePath属性？

Great question! Unfortunately, as of right now, the VS Code C/C++ extension doesn’t offer a built-in syntax like ${workspaceFolder:Secondary:includePath} to directly reference the includePath entries from another workspace folder’s c_cpp_properties.json. The manual copy-paste approach you’re using works, but it’s definitely not ideal for scaling—especially when dealing with lots of include paths or multiple dependent projects.

Here are a few cleaner alternatives to avoid duplicate configuration:

1. 使用工作区级自定义变量 #

You can define a shared set of include paths in your multi-root workspace’s .vscode/settings.json (not the individual folder settings), then reference this variable in both project’s c_cpp_properties.json files. This way, you only update the paths in one place.

Step 1: Define the shared variable #

In your workspace-level .vscode/settings.json:

{
  "project.sharedSecondaryIncludes": [
    "${workspaceFolder:Secondary}/Include",
    "${workspaceFolder:Secondary}/Subdir1/Include",
    "${workspaceFolder:Secondary}/Subdir2/Include"
  ]
}

Step 2: Reference the variable in each project’s config #

In Main’s c_cpp_properties.json:

{
  "configurations": [
    {
      "name": "Linux", // 或者你的目标平台（比如Win32、macOS）
      "includePath": [
        "${workspaceFolder}/**",
        "${config:project.sharedSecondaryIncludes}"
        // 其他本地include路径
      ],
      // 剩余配置（比如defines、compilerPath等）
    }
  ]
}

You can also use the same variable in Secondary’s own c_cpp_properties.json to keep its configuration consistent too.

2. 用CMake自动同步配置（如果项目使用CMake） #

If your projects use CMake for building, you can let the VS Code C/C++ extension auto-generate the includePath based on your CMake configuration. This eliminates manual editing of c_cpp_properties.json entirely.

Just ensure you have the CMake Tools extension installed, then set up your CMakeLists.txt with include_directories() for your Secondary project’s include paths. The extension will automatically sync these paths into the VS Code intellisense configuration, keeping everything in sync as your project evolves.

3. 符号链接（跨平台需注意） #

If you’re working on a system that supports symbolic links (Linux/macOS, or Windows with Developer Mode enabled), you can create symlinks from Main’s directory to Secondary’s include folders. This way, Main can reference the includes as if they’re local, without duplicating paths in config files.

For example, on Linux:

ln -s ../Secondary/Include ./Main/SecondaryInclude

Then in Main’s c_cpp_properties.json, you just need to add ${workspaceFolder}/SecondaryInclude (and any other symlinked folders) to your includePath. Note that this approach can have cross-platform compatibility issues if your team uses mixed operating systems.

内容的提问来源于stack exchange，提问作者Andrew Matthews