-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config UI shows incorrect error message that compilerPath
is not found, despite picked up correctly from PATH
#11903
Comments
Hi @geissdoerfer . I believe the error message you are seeing is incorrect and a bug in our path validation in the Config UI. However, using a relative path should actually function correctly. Using a simple example, using We can use this issue to track correcting the invalid error message in the Config UI. |
compilerPath
is not found, despite picked up correctly from PATH
Environment
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:
When specifying
"compilerPath": "arm-none-eabi-gcc"
inc_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
Other Extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: