Usage with cmake-js/scikit-build/scikit-build-core and other cmake wrappers

[segevfiner]

There are some tools like cmake-js, scikit-build, and scikit-build-core, used to build extension/addon modules for Node.js and Python respectively that drive cmake by themselves, passing it additional definitions and so on that the CMakeLists.txt file of the addon expects.

I wonder what's the best way to configure this to interop nicely with vscode-cmake-tools, as by default this extension wants to drive the cmake configure/build by itself, and has it's own default build directory.

[gcampbell-msft]

@segevfiner Currently there is not a great way for users to configure the extension to make this interop nicely.

It's possible that you could point the cmake.cmakePath setting to your wrapper scripts that you mention, but it would still be utilized in the same way as cmake.exe, where we attempt to drive the configure and build ourselves. Based on your explanation of the tools you mention, this likely still isn't what you want.

We're happy to consider this as a feature request if you create an issue for it, but to be fully transparent our design is primarily to use cmake.exe and drive the configure and build ourselves, so it's not something that we'd likely implement right now. Thanks for your feedback and discussion post!