microsoft / microsoft/vscode-cpptools

Add system include path support for pre-VS2015 compilers

Open
#3,687 12 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Request Feature: Compile Commands Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

I'm trying to get my Windows set up to work properly, but at the moment I get errors saying it can't find source files even though I can control+click on the files and open them.

Config:

{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\include",
                "C:/Users/nscott/workspace/asldev/aslcore/",
                "C:/Users/nscott/workspace/qt4/qt4/include"
            ],
            "browse": {
                "limitSymbolsToIncludedHeaders": true,
                "databaseFilename": "",
                "path": [
                    "C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/include/",
                    "C:/Users/nscott/workspace/asldev/aslcore/",
                    "C:/Users/nscott/workspace/qt4/qt4/include",
                    "${workspaceRoot}"
                ]
            },
            "defines": [
                "_DEBUG",
                "UNICODE"
            ],
            "intelliSenseMode": "msvc-x64",
            "compileCommands": "C:\\w\\build_x86_debug\\compile_commands.json"
        }
    ],
    "version": 4
}

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows configuration with a pre-VS2015 compiler, focusing on how includePath, browse.path, and compileCommands are interpreted. Trace the C/C++ extension entry point that resolves system headers and compare behavior for the Visual Studio 10.0 include directory; done means those headers resolve without source-file errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript
Domain
compilers, developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.