-
Notifications
You must be signed in to change notification settings - Fork 449
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
Do not crash with cmake 3.7-3.13 with CMakePresets.json present #2026
Comments
Possible fix: vscode-cmake-tools/src/cmake-tools.ts Lines 1998 to 2007 in e767115
Since the instance |
@xisui-MSFT could you take a look at this? |
This issue can be reproed using setting |
A build with this fix is available for you to test. Could you download the VSIX from here: https://github.com/microsoft/vscode-cmake-tools/suites/3599000085/artifacts/86773353 then unzip the file and run the "Install from VSIX..." command in VS Code to install it and try it out? |
@bobbrow The VSIX download link is not found. |
Hmm... it works for me. Can you try this one instead? |
The fix for this was released today in version 1.8.1 |
Brief Issue Summary
Do not crash with cmake 3.7-3.13 with
CMakePresets.json
present.If I start VScode directly (cmake auto-detected version is 3.12), or start VSCode in VS2017 command prompt (cmake version is 3.12), this problem exists.
If I start VSCode in Ubuntu 18.04 (cmake from ubuntu bionic is 3.10), this problem exists.
If I start VSCode in VS2019 command prompt (cmake version is 3.20), there is no problem.
If I start VSCode in Ubuntu 20.04 (cmake from focal is 3.16), there is no problem.
Open a workspace with
CMakePresets.json
present.CMakePresets.json
Expected:
No Configure Preset Selected is available for choosing configure preset.
Apparent Behavior:
Configure Presets list is not available.
If No Configure Preset Selected clicked, a toast shows command 'cmake.selectConfigurePreset' not found
CMake Tools Log
Platform and Versions
Platform and Versions
Other Notes/Information
The text was updated successfully, but these errors were encountered: