Does CMake Integration replace CMake Tools?

[Yzrsah]

Please provide some basic docs about CMake Integration vs the CMake Tools extension

• Differences between CMake Integration and CMake Tools extensions
• Some key points to use CMI instead of CMT

If the extensions are incompatible, then you should also remind the user to disable other extensions such as CMake Tools.

[go2sh]

Both extension basically try to do the same and they are somewhat incompatible as they share some settings, keybindings and both operate on the build directory.

CMake Tools has a few drawbacks, which made me to start this extension:

• No multi workspace folder support
• No multi workspace folder dependencies

For me, the goal of this extension is to fully replace CMake Tools and provide the same set of features at least. In my own projects, I already did that.

Initially, I thought about adding those things to CMake Tools, but the code base has some major design flaws, which meant that the extension had to be rewritten anyways. Furthermore, CMake Tools uses rollbar, which I'am not a big fan of due to data protection concerns.

This extension currently lacks some features, that CMake Tools already has:

• Build Configuration (aka Kits and Variants)
• CMake Tree View

If you find any bug or you are missing a feature, feel free to create a new issue. I'll add a reminder to the README to disable the CMake Tools Extension as both are incompatible.

[hriekehof]

What about the Cpp-tools integration from Microsoft for intellisense ? This is also a nice feature in the cmake-tools extension

[go2sh]

@hriekehof This extension has it also. In addition to the cmake-tools extension , It provides infos for non source files (like header etc.) for all workspace folders.

[go2sh]

Add added a remark to the readme about the incompatibility.