Selecting a Kit without a compatible cmake generator breaks all builds until restart. #512
Labels
bug
a bug in the product
crash
causing a crash in either VS Code or the extension itself
Feature: configure
fixed (release pending)
fixed in pre-release and is pending official release
Milestone
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: