8000 Make the extension look for the compiler in the PATH environment variable as well · Issue #12779 · microsoft/vscode-cpptools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Make the extension look for the compiler in the PATH environment variable as well #12779

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.

Sign up for GitHub

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

Jump to bottom
Open
luizfernandonb opened this issue Sep 27, 2024 · 4 comments
Open

Make the extension look for the compiler in the PATH environment variable as well #12779

luizfernandonb opened this issue Sep 27, 2024 · 4 comments
Labels
bug compiler support Feature: Configuration An issue related to configuring the extension or IntelliSense Language Service
Milestone
1.26

Comments

@luizfernandonb
Copy link
luizfernandonb commented Sep 27, 2024 •
edited
Loading

Feature Request

Currently we have to put the full path of the compiler in the compilerPath property in c_cpp_properties.json, and this breaks portability between systems, since the paths between Windows and Linux are different, would it be possible to put only the name of the compiler and the extension to search for the executable in the PATH environment variable?

Example: "compilerPath": "C:/Program Files/Clang/bin/clang.exe" -> "compilerPath": "clang"
@Colengms
Copy link
Contributor

Hi @luizfernandonb . I'm going to consider this a bug. I believe this did work at one time and may have regressed.

@Colengms Colengms added bug Language Service Feature: Configuration An issue related to configuring the extension or IntelliSense compiler support labels Sep 27, 2024
@Colengms Colengms added this to the 1.22.7 milestone Sep 27, 2024
@luizfernandonb
Copy link
Author

@Colengms

Just to add, the same goes for clang-tidy, it's on my path
image

However, the extension downloaded a version and uses it instead of the one in the PATH
image

And I didn't fill anything in the extension settings
image

@sean-mcmanus
Copy link
Contributor
sean-mcmanus commented Sep 30, 2024 •
edited
Loading

I believe the clang-tidy/format issue is tracked by #12718 (it currently doesn't use the environment version if it's older, which was due to many users having an old version on their machine that causes stuff to not work).

@sean-mcmanus sean-mcmanus modified the milestones: 1.22.7, 1.22, 1.23 Sep 30, 2024
@sean-mcmanus sean-mcmanus modified the milestones: 1.23, 1.24 Jan 10, 2025
@sean-mcmanus sean-mcmanus modified the milestones: 1.24, 1.25 Apr 2, 2025
@sean-mcmanus sean-mcmanus modified the milestones: 1.25, 1.26 Apr 29, 2025
@heartacker
Copy link
Contributor

eye

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug compiler support Feature: Configuration An issue related to configuring the extension or IntelliSense Language Service
Projects
cpptools
Status: No status
Milestone
1.26
Development

No branches or pull requests
4 participants
@heartacker @sean-mcmanus @luizfernandonb @Colengms
0