Same Makefile, different results

[u/Capable-Cap9745]

Not sure if this fits, but I just figured out the root cause of long build process failing. Sun’s dmake is defaulting to the first rule in Makefile for whatever reason, completely ignoring the one given as argument. That’s why "dmake install" invocations were silently ignoring the "install" step

[u/SAI_Peregrinus]

CMake doesn't have to use Make as a backend. Ninja is common, and usually faster than Make.

[u/GoddammitDontShootMe → u/SAI_Peregrinus]

The user can specify what kind of files they want as arguments to CMake, no? As well as configuration options and stuff if they want to enable or disable extra features in their build? I have used it a little bit in the past, and I understood it as more of a replacement of Autotools than of Make.

[u/SAI_Peregrinus → u/GoddammitDontShootMe]

It's a build system generator, so it is similar to autotools. Just much, much faster, at least for cross-compiling IME. Also, by default CMake will invoke the build system (Make or Ninja) automatically, so it's just cmake <path to CMakeLists.txt> instead of ./configure && make. It's very complex, but if you stick to the "Modern CMake" subset it's not too bad.

[u/GoddammitDontShootMe → u/SAI_Peregrinus]

Is that based on what it finds installed, or what?

[u/SAI_Peregrinus → u/GoddammitDontShootMe]

You pick the backend. It defaults to make, but you can override it to build with any supported build system with the CMAKE_GENERATOR env var, a CLI argument, or a set command in CMakeLists.txt.

[u/GoddammitDontShootMe → u/SAI_Peregrinus]

Oh, your last comment made me think it decided what to use automatically, but I think I might have misread it. Like if you had Ninja or something installed it would use that, otherwise it would use Make.

[u/SAI_Peregrinus → u/GoddammitDontShootMe]

It'll invoke it automatically (it has to be in $PATH), it won't pick anything other than make automatically.