-
Notifications
You must be signed in to change notification settings - Fork 461
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
CMake Tools Not Available as C++ Configuration Provider #1832
Comments
CMake Tools does not currently register itself until a successful "configure" has happened. We recommend setting |
Thanks. I tried running "CMake: Configure" and then changing the provider, but CMake Tools was still not available. |
Did the configure fail? I don't know of any other reason why this shouldn't work. Is this on the CMake repo, or some other one? |
The configure succeeded. I just tried it a second time and was still not able to change the configuration provider. I am working on the CMake repository, but I'm using |
Thanks. I emailed you the debug log in private. |
@xisui-MSFT, @andreeis, The configuration provider doesn't get registered when presets are active. I traced it to here: vscode-cmake-tools/src/extension.ts Line 663 in 4d242c7
There is no active Kit when presets are used, so the provider never registers. This code depends on Kits, so we'll need to update this section to work with either Kits or Presets. |
@KyleFromKitware, we have a fix for this problem. Until we release 1.7.3 (soon today or tomorrow) you can try the vsix here: https://github.com/microsoft/vscode-cmake-tools/suites/2718070085/artifacts/59903576. |
This fixes it for me. I updated the version in package.json to 1.7.3. We just need to update the changelog and we can release it. |
Brief Issue Summary
I'm trying to use CMake Tools as the C++ configuration provider, but it is not available when I go to "C/C++: Change Configuration Provider..."
Expected:
Apparent Behavior:
Platform and Versions
Other Notes/Information
I am using
CMakeUserPresets.json
, not sure if this is relevant or not.The text was updated successfully, but these errors were encountered: