Environment
- OS and Version: Windows 11
- VS Code Version: 1.125.1
- C/C++ Extension Version: 1.33.4
- If using SSH remote, specify OS of remote machine:
Bug Summary and Steps to Reproduce
The ms-vscode.cpptools extension fails to evaluate the PATH variables provided by e.g. a CMake preset, terminal.integrated.env.windows or cmake.environment (or any other cmake.*Environment) variables, nor is there an option to explicitly specify a PATH environmental variable to be used by the extension, like C_Cpp.path.
This results in the build environment not being detected correctly. IntelliSense and code completion does not work.
Building via the ms-vscode.cmake-tools extension works perfectly fine, since it is evaluating the environment specified in a CMakePresets.json (s. excerpt):
{
"configurePresets": [
{
"name": "<PRESET_NAME>",
"displayName": "'<PRESET_NAME>' config",
"description": "'<PRESET_NAME>' configure using 'Unix Makefiles' generator",
"generator": "Unix Makefiles",
"environment": {
"PATH": "<PATH_TO_COMPILER_ROOT>/sysroots/x86_64-petalinux-mingw32/usr/bin:$penv{PATH}"
}
}
],
}I do not want to alter the PATH environmental variable of the system, in order not to create conflicts with other projects I am working on. This means I have to manually specify the path every time in a CMD.exe,
C:\PATH\TO\PROJECT>set PATH=<PATH_TO_COMPILER_ROOT>\sysroots\x86_64-petalinux-mingw32\usr\bin;%PATH%
C:\PATH\TO\PROJECT>code .
or create a batch file, to start code with the correct environment.
Am I missing a way how to set the environment, particularly for a project - not system wide?
Could you please add a feature to set the PATH used by ms-vscode.cpptools ? Ideally the one from the CMake preset is automatically used.
Configuration and Logs
[7/10/2026, 12:12:00 PM] Unable to resolve configuration with compilerPath "<PATH_TO_COMPILER_ROOT>/sysroots/x86_64-petalinux-mingw32/usr/bin/aarch64-xilinx-linux/aarch64-xilinx-linux-g++.exe". Using "cl.exe" instead.
Other Extensions
No response
Additional context
No response
Environment
Bug Summary and Steps to Reproduce
The
ms-vscode.cpptoolsextension fails to evaluate thePATHvariables provided by e.g. a CMake preset,terminal.integrated.env.windowsorcmake.environment(or any othercmake.*Environment) variables, nor is there an option to explicitly specify aPATHenvironmental variable to be used by the extension, likeC_Cpp.path.This results in the build environment not being detected correctly. IntelliSense and code completion does not work.
Building via the
ms-vscode.cmake-toolsextension works perfectly fine, since it is evaluating the environment specified in aCMakePresets.json(s. excerpt):{ "configurePresets": [ { "name": "<PRESET_NAME>", "displayName": "'<PRESET_NAME>' config", "description": "'<PRESET_NAME>' configure using 'Unix Makefiles' generator", "generator": "Unix Makefiles", "environment": { "PATH": "<PATH_TO_COMPILER_ROOT>/sysroots/x86_64-petalinux-mingw32/usr/bin:$penv{PATH}" } } ], }I do not want to alter the
PATHenvironmental variable of the system, in order not to create conflicts with other projects I am working on. This means I have to manually specify the path every time in a CMD.exe,or create a batch file, to start
codewith the correct environment.Am I missing a way how to set the environment, particularly for a project - not system wide?
Could you please add a feature to set the
PATHused byms-vscode.cpptools? Ideally the one from the CMake preset is automatically used.Configuration and Logs
Other Extensions
No response
Additional context
No response