8000 Config UI shows incorrect error message that `compilerPath` is not found, despite picked up correctly from PATH · Issue #11903 · microsoft/vscode-cpptools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Config UI shows incorrect error message that compilerPath is not found, despite picked up correctly from PATH #11903
Closed
@geissdoerfer

Description

@geissdoerfer

Environment

  • OS and Version: Arch Linux x64 6.6.10-1-lts
  • VS Code Version: 1.85.2
  • C/C++ Extension Version: v1.18.5

Bug Summary and Steps to Reproduce

Bug Summary:

I have a project opened in vscode in the directory /home/myuser/myworkspace. arm-none-eabi-gcc is on my PATH:

myuser@mymachine ~> arm-none-eabi-gcc --version
arm-none-eabi-gcc (Arch Repository) 13.2.0

When specifying "compilerPath": "arm-none-eabi-gcc" in c_cpp_properties.json, the following problem is reported: Cannot find "/home/myuser/myworkspace/arm-none-eabi-gcc".

Expected behavior:

Since compilerPath is specified as a relative path, I would expect that it is found on my PATH. This seems to be the intended behavior implemented with 5ca9f34.

Configuration and Logs

`c_cpp_properties.json`:


{
    "configurations": [
        {
            "name": "${config:operSys}",
            "includePath": [
                "${config:rioteeSdkRoot}/core/include",
            ],
            "defines": [
                "mcpu=cortex-m4",
            ],
            "compilerPath": "arm-none-eabi-gcc",
            "intelliSenseMode": "gcc-arm",
            "cStandard": "c17",
            "cppStandard": "c++14"
        }
    ],
    "version": 4
}
``

Other Extensions

No response

Additional context

No response

Metadata

Metadata

Assignees

Labels

Feature: ConfigurationAn issue related to configuring the extension or IntelliSenseLanguage ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0