microsoft / microsoft/vscode-cpptools

Cannot open "stdarg.h" with arm-none-eabi-gcc cross-compilation project on windows with cmaketools

Open
#6,665 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Similar error here on simple arm-none-eabi-gcc cross-compilation project on windows with cmaketool as configuration provider.

Steps to reproduce:

Windows 10,
Install arm-none-eabi-gcc and cmake, added them to user path
Checkout my dedicated repo
Open folder blinky
autorise Cmaketools to configure intellisense
open file stm32l4xx_hal_conf.h then IntelliSense will provide same error.

If you guide me I can provide any necessary information.
(notify @hish15 as he is able to reproduce)

Originally posted by @atsju in https://github.com/microsoft/vscode-cpptools/issues/5349#issuecomment-743769047

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

Reproduce the issue using the linked IssueCppTools5349 repository on Windows with arm-none-eabi-gcc and CMake Tools. Open blinky/stm32l4xx_hal_conf.h after authorizing CMake Tools to configure IntelliSense, then trace why stdarg.h is not found; done means the error no longer appears for this cross-compilation setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp, vscode
Domain
compilers, devtools, tooling
Issue type
Bug
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.