-
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
Latest v1.19.4 update produces: Unable to resolve configuration with compilerPath "C:/Program Files/LLVM/bin/clang-cl.exe". Using "cl.exe" instead. #12024
Comments
@jahn00 We need more repro info. Can you confirm that it doesn't repro if the "compileCommands" property is commented out? I believe an argument in that compile_commands.json is triggering the issue. If you set C_Cpp.loggingLevel to "Debug" and look at the C++ logging output window you should see some error related to querying of the clang-cl.exe compiler with some particular args which we may not be handling correctly, so if you could provide that logging or let us know which args are triggering the failure then we can fix the issue. Also, what version of LLVM/clang are you using? Also, it sounds like the bug doesn't repro with 1.18.5 (i.e. the recommended workaround would be to downgrade to that until we can release a fix). |
No repro on previous version, 1.18.5, no repro when commenting out compileCommands C++ log output after setting to "Debug": https://pastebin.com/H121W2rs LLVM version 16.0.0, not 17 due to compatibility with intellisense. FWIW, I'm working in Microsoft Edge/Chromium. |
Hi @jahn00 . The C/C++ Extension will attempt to invoke your compiler to auto-detect system include paths and defines. If you look into the log, you'll see some command lines that were attempted. Do these command lines work properly for you, if you execute them manually? If not, you will likely see the same error the extension is encountering. Running a command line from your log with clang-cl.exe 16, I get the following error:
When this type of issue is due to the C/C++ Extension failing to properly parse the original command line or compose a query command line, it's usually straight-forward for us to address that, provided the original command line used for configuration and the logged attempted command line. Could you provide an example command line from your |
I'm reproing this to - i have to go back to v1.19.2 to have any luck, and am currently using llvm 17 |
1_19_2.log |
@sean-mcmanus - I Updated to 1.19.5 and went down from infinite errors to ~56 errors in configuration warnings. Looking at the debug log, |
LOL
The only difference here is the relative pathing and the "/" vs "\" also looking at my log, it's failing to find include paths from the compiler command line that are relative paths. snippet:
|
Hi @jahn00 . I see this error in your log:
In 1.19.x, we fixed a bug where the I also see the following:
This is a deprecation message, so I would have assumed it would be a warning. We should probably remove occurrences of |
yes, the directory field is: this doesn't repro in 1.19.2 |
Hi @jahn00 . The fix to properly use the contents of the I have a
And the currently open workspace folder is This seems to work as expected. Any changes to that path in the Can you confirm the full path to your workspace folder, to |
Environment
OS and Version: Win 11 Pro 22631.3155
VS Code Version:
Version: 1.86.2 (user setup)
Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:40:56.878Z
Electron: 27.2.3
ElectronBuildId: 26908389
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.22631
C/C++ Extension Version: 1.19.4
If using SSH remote, specify OS of remote machine:
Bug Summary and Steps to Reproduce
Bug Summary:
VSCode C++ extension no longer detecting my C++ compiler
Steps to reproduce:
repeatedly.
Expected behavior: No error output on launch.
Configuration and Logs
Other Extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: