microsoft / microsoft/vscode-cpptools

Documentation request how to specify include firs for intelisense and defines

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

Nobody has claimed this yet.

docs Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Feature Request

We build with makefile cross compiling

An in my makefile I can add a target to create a file that lists sec firs and include firs and active # defines for intellisense

what does not work is having viscose just select all h files under the project root for

reason: I have different( multiple) chip drivers in different sub directories the makefile has a macro/variable that controls the active target and configuration

Example top dir is BSP and under that dir are 5 different boards something like this
BSP/boardname/include/board gpio.h
and BSP/src/board gpio.c

thus a makefile target can create a file for intelisense

part 2 is how do I tell vs-code to forget and delete the intellisense database because it is lost or the configuration has changed and it needs to be rebuilt

what files do I delete to make that happen

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 with the Makefile target that emits include directories and active #defines, then compare it with the VS Code IntelliSense configuration and database behavior. Update documentation to cover both selecting the generated configuration for the BSP/board layout and the supported way to force a rebuild; done when both questions have explicit steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cpp
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.