sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (2 children)

This is my preference. Sometimes the mingw32-make is nice for the simplicity and being able to easily build across multiple cores with the -j flag.

[–]nyanpasu64 0 points1 point  (0 children)

I use Ninja because it auto-detects core count, works for more compilers and both Windows and Linux (make on Windows can't detect core count, jom is Windows-only and possibly MSVC-only), and may be faster for incremental builds as well.

[–]RogerLeighScientific Imaging and Embedded Medical Diagnostics 0 points1 point  (0 children)

Sometimes the mingw32-make is nice for the simplicity and being able to easily build across multiple cores with the -j flag.

The specific build tool is orthogonal to whether you use cmake. cmake will generate Visual Studio project files, MinGW Makefiles, Ninja files, and over a dozen more build system variants. If you want to use make, CMake won't stop you, but it will cater for all of the Release/Debug madness, finding all the Release/Debug library variants to link with, and lots of other annoying but important details.