-
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
Selecting a Kit without a compatible cmake generator breaks all builds until restart. #512
Comments
I'll take a look. Stray exceptions breaking things... |
Sorry, but this one will have to be pushed back. 1.1.2 is long overdue and I've already closed all the ready-to-fix issues. Will push in next release. |
This issue has been addressed in CMake Tools 1.2.0 which is available in the VS Code Marketplace or on the Releases Page Because the publisher id has changed, VS Code does not automatically upgrade you yet. The Marketplace team will enable this in the next few days. If you want to install 1.2.0 now, please make sure you uninstall any earlier versions of CMake Tools manually to avoid any conflicts. |
Brief Issue Summary
The error message "[rollbar] Unhandled exception: Unhandled Promise rejection: build Error: Unable to determine CMake Generator to use {}" prevents me from building after selecting the MinGW toolchain. It also breaks Visual Studio kits in my case -- I've used the Visual Studio kits on Windows with before successfully, but after adding C:\MinGW\bin to the Path variable, the scan recognized the GCC and now refuses to build with any kit.
Expected:
Starting any cmake addin command (Configure, Build, Debug Target) will start cmake / the selected compiler / the target.
Apparent Behavior:
Output tab opens in the CMake/Build view mode, and shows a single-line error message.
In the developer log, it seems as if the change kit command actually fails to switch away from GCC back to the good kits. The bottom toolbar however also doesn't update, and always shows "VisualStudio 14.0 - x86" (the last good selection) after choosing the GCC kit -- no matter what kit I choose afterwards.
Restarting VisualStudio Code fixes the issue with MSVC temporarily until I select GCC as toolchain again.
CMake Tools Log
Developer Tools Log
Platform and Versions
Other
Setting cmake.generator to "Unix Makefiles" only helps before this error state is reached; afterwards, it's completely ignored.
The text was updated successfully, but these errors were encountered: