vscode-cmake-tools: Bad CMake executable message appears erroneously
While investigating #2361, it appears that the “Bad CMake executable” message appears one more time after fixing the cmake.cmakePath setting and saving the settings.json file. Despite the message, the save works and the new cmake.cmakePath setting is used in the next Configure operation.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 17 (8 by maintainers)
Fix is merged in and should be included in the 1.15 release.
Apparently it’s always been this way. I’m adding a 👍 to this issue in hopes that they’ll redesign it: https://github.com/microsoft/vscode/issues/50827
Though, honestly, I almost always use the JSON view for settings.
You can’t clear it by deleting the contents, you have to use the gear icon. The blue line to the left of the setting indicates that it has a value (empty string in this case).