Vscode-cmake-tools: The 'cmake-server(7)' is deprecated.

[Colengms]

Perhaps obvious, but just wanted to point out that with CMake 3.15 installed, I get the following warning when configuring:

CMake Deprecation Warning:
The 'cmake-server(7)' is deprecated. Please port clients to use the
'cmake-file-api(7)' instead.

[jnickborys]

Bumping this. I hit it too.

[rustedwizard]

Same here.

[Ian-Re]

same here.

[JesvinJoseph]

same here

[tkit1994]

Same here.

[cestlascorpion]

same here. And how can I use the "cmake-file-api(7)" instead?

[Zingam]

You can't. That's a task for the extension to implement. I have looked up the sources and I am not sure if that would be a trivial task. So I don't expect that to change soon but for now I don't think that this warning message should bother you.

[RTS007]

Same here.

[Toxe]

In the meantime, is there any way to disable this warning?

[Randshot]

From what I know, this requires significant changes in core parts of the extension, so I think that we won't see any update on this soon, depending on how many people are actively involved in maintaining this extension.

[bobbrow]

I believe @KoeMai's PR implements this https://github.com/microsoft/vscode-cmake-tools/pull/720. I haven't had a good chunk of time to review it yet, but it's on my short list.

[Randshot]

Oh, didn't see that one. Looks promising, but like I expected a rather large effort.

[nmoinvaz]

Uninstalling cmake 3.15 and installing the previous version 3.14.6 appears to work for me. Obviously its not a long term solution.

[eddyekofo94]

Any fix thus far?

[eddyekofo94]

CMake has this on their CMake 3.15 Release Notes.

[timxian]

Off-topic: Is anybody running VSCode + CMake 3.15 (particularly CMake form the snap package) on Ubuntu?

here

[FISHFISHFISHLOVECAT]

Same here

[SerkZex]

Are there a fix for this?

[roy-tian]

I set "cmake.useCMakeServer" to "false" and the warning was gone.

[bobbrow]

The warning can be ignored for now. It doesn't harm the experience. We plan to add support for cmake-file-api soon.

[Zingam]

I set "cmake.useCMakeServer" to "false" and the warning was gone.

@roy-tian Please, don't do that! You've just ruined your whole experience :)

[siriobalmelli]

The problem at this time seems to be:

Setting "cmake.useCMakeServer": false:

• I get no list of build targets
• Manually entering a build target builds cleanly
• I cannot seem to find an option to manually specify targets in settings.json; I have looked here and here

Setting "cmake.useCMakeServer": true:

• I do get a list of build targets
• I get a crash when trying to run a build:

[cms-client] The connection to cmake-server was terminated unexpectedly
[cms-client] cmake-server exited with status null (SIGSEGV)

Notes

This behavior is identical on cmake versions 3.15.4 and 3.14.7, only tested on macOS.

It appears that the cmake server may not behave the same as the file API?
See here for an example.

Unfortunately I cannot edit the CMakeLists.txt in question because:

• it is a manufacturer's SDK
• it does legitimately work when running cmake on the command line.

This may possibly be related to:

• https://github.com/microsoft/vscode-cmake-tools/issues/752
• https://github.com/microsoft/vscode-cmake-tools/issues/688

Conclusion

Perhaps the simplest solution for now is to provide a configuration setting to manually specify targets in settings.json?

I'm at an impasse with this, any recommendations are welcome.

[Zingam]

@siriobalmelli If you are experience a crash, you should create a new issue. This feels like a CMake bug to me, so maybe report it there too.

_File API is an alternative (new) way of IDEs to communicate with CMake. This warning is not a real issue, so you should just ignore it. I don't know if it can be disabled. The next version of the extension will probably support File API so it is not worth bothering doing it._

[grownanny]

same issue when setting up make is VScode

[bobbrow]

This was addressed in 1.3.0