Bad CMake executable message appears erroneously

[bobbrow]

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.

[H-G-Hristov]

I just found out (I think) that Workspace setting always overwrites User even if it is empty. So basically I am unable to use CMake from a shared directory between macOS host/Linux on a VM.
So i attempted to set CMake location in User but I get

Bad CMake executable "". Is it installed or settings contain the correct path (cmake.cmakePath)?

[bobbrow]

Yes, Workspace and Folder settings always override User. I'm not 100% clear on what you're trying to do though. Are you setting "cmake.cmakePath": "" in the Workspace setting? That will never work.

[H-G-Hristov]

Yes, I tried that. So we can't have a global setting for cmake.cmakePath or am I doing something wrong?

[bobbrow]

If you don't set anything for cmake.cmakePath in Workspace or Folder settings, then User settings will be used. So if the User setting would work for both workspaces, then delete whatever you set for cmake.cmakePath in Workspace and Folder settings.

[H-G-Hristov]

So I use the same folder on a Mac. I'm accessing it also via Virtual Box which has Linux. Linux uses snaps so I need to explicitly set: cmake.cmakePath to /snap/cmake/current/bin/cmake but then this breaks my Mac settings :)

[H-G-Hristov]

If you don't set anything for cmake.cmakePath in Workspace or Folder settings, then User settings will be used. So if the User setting would work for both workspaces, then delete whatever you set for cmake.cmakePath in Workspace and Folder settings.

If I clear:

I get: Bad CMake executable "". Is it installed or settings contain the correct path (cmake.cmakePath)?

[bobbrow]

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).

[H-G-Hristov]

This setting sets it to "cmake".

[bobbrow]

Yes, that's the default value, but that value is not used because you didn't explicitly set it. You should see something like this that indicates it is set in the User settings.

[bobbrow]

I feel like VS Code used to show the User value if you didn't set it in Workspace settings. This looks confusing and perhaps is a regression from previous versions.

[bobbrow]

I just cleared my Workspace setting, set something bogus in User so I could get the message (I'm on Windows currently), and it does pick up the User setting:

[H-G-Hristov]

That's confusing! Thank you!

[bobbrow]

Apparently it's always been this way. I'm adding a 👍 to this issue in hopes that they'll redesign it: microsoft/vscode#50827

Though, honestly, I almost always use the JSON view for settings.

[H-G-Hristov]

Just for the record. Another workaround: #838 (comment)

[Juanc179]

Hi, im running into the same problem. I checked my cmake path and it's like it should be. anyways, it doesn't detect it or it is missing something.

[Sinetian]

bad. Hopes it will be fixed.

[andreeis]

Fix is merged in and should be included in the 1.15 release.