Skip to content
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

"Select IntelliSense Configuration" and Run&Debug button do not offer user-specified compilerPath #10943

Closed
Colengms opened this issue May 12, 2023 · 3 comments
Assignees
Labels
bug Feature: Configuration An issue related to configuring the extension or IntelliSense fixed Check the Milestone for the release in which the fix is or will be available. Language Service quick fix
Milestone

Comments

@Colengms
Copy link
Contributor

Repro steps:

  • Install a non-standard C++ compiler into an arbitrary location. My repro was using a compiler toolchain downloaded here: https://github.com/mstorsjo/llvm-mingw/releases
  • Specify a path to that compiler in the compilerPath field of c_cpp_properties.json. (IntelliSense properly queries the compiler and uses its settings for IntelliSense). In my case, this was; "compilerPath": "Z:\\llvm-mingw-20220906-msvcrt-x86_64\\bin\\clang++"
  • Use either the "Select IntelliSense Configuration" command or click on the "Debug C++ file" (run and debug) button.
    image

Note that the compiler specified in compilerPath is not offered as an option on either of those lists.

Also, there are two similarly named commands: "C/C++: Select IntelliSense Configuration..." and "C/C++: Select a Configuration...". Perhaps these names could be revisited to make them less ambiguous.

@Colengms Colengms added bug Language Service Feature: Configuration An issue related to configuring the extension or IntelliSense labels May 12, 2023
@Colengms Colengms added this to the 1.16 milestone May 12, 2023
@Colengms
Copy link
Contributor Author

The Run & Debug scenario is more obviously wrong, as the user should be able to build using the same compilerPath they've configured IntelliSense with.

@sean-mcmanus
Copy link
Contributor

@Colengms What did you have in mind for the command names? That's a completely separate issue so I'm not sure why it's added to this issue. "C/C++: Select IntelliSense Configuration..." is short for "C/C++: Select IntelliSense Configuration Source..." but I was worried that would be too long.

@sean-mcmanus sean-mcmanus modified the milestones: 1.16, 1.16.0 May 17, 2023
@bobbrow bobbrow linked a pull request May 17, 2023 that will close this issue
@bobbrow bobbrow removed a link to a pull request May 17, 2023
@sean-mcmanus sean-mcmanus added the fixed Check the Milestone for the release in which the fix is or will be available. label May 19, 2023
@michelleangela
Copy link
Contributor

@github-actions github-actions bot locked and limited conversation to collaborators Jul 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Feature: Configuration An issue related to configuring the extension or IntelliSense fixed Check the Milestone for the release in which the fix is or will be available. Language Service quick fix
Projects
None yet
Development

No branches or pull requests

3 participants