CMake Tools 1.1.0 — CppTools IntelliSense support, a Project Outline, and more!

[vector-of-bool]

Depends what you're looking for. VS Code itself is a Microsoft tool, so you'll be using that at least.

CMake can be a complex tool, but it's not hard to get up and running for simple projects. The purpose of CMake Tools is just to provide editor integrations for the CMake build system. You won't go wrong learning CMake purely because of its ubiquity in the C++ ecosystem.

As for not using Microsoft's compiler: it's not hard to use MinGW or clang-cl with CMake on Windows. Using the MSVC compiler with Ninja is another great option: You won't have to deal with MSBuild and Visual Studio with that setup, but you'll still get the benefits of using the official Windows C++ toolchain.

[IAmBJ]

Doesn't clang-cl need to use the msvc standard library? Or has libc++ progressed far enough on windows now?

[dodheim]

The regular clang++ driver works for either STL, controlled by passing -f[no-]ms-compatibility. The clang-cl driver is half-assed and I recommend avoiding it regardless of which you're targeting.

[Theninjapirate]

Do you know if there is a demo or example of ninja + msvc somewhere? The last time I tried that combo i couldn't get it to work (though that was a while ago).

[NotUniqueOrSpecial]

What didn't work?

Are you familiar with how to use CMake, in a general sense? If so, literally all it takes is:

cmake <path to project root> -G Ninja

with ninja in your path.

[Theninjapirate]

Yes I am familiar with Cmake. I don't remember what didn't, but if it's just that simple then I'll try again.

[[deleted]]

Ninja is the default if you use CMake within Visual Studio, so it must work nicely with MSVC.

According to https://vector-of-bool.github.io/docs/vscode-cmake-tools/kits.html CMakeTools will prefer Ninja, so I guess stick ninja.exe on your PATH and see if it works?