I (the author of Ninja) think tup is a fine choice for your project. Ninja was designed to work within a specific pragmatic context: a very large project (Chro

I (the author of Ninja) think tup is a fine choice for your project. Ninja was designed to work within a specific pragmatic context: a very large project (Chrome) that had existing constraints on how the build works. (This design also makes Ninja suitable for use from CMake, which means you can use Ninja to build e.g. LLVM in a manner faster than the existing alternatives.) Here is a longer post on the subject. https://groups.google.com/group/ninja-build/msg/b52e7d3b77bb2e2c https://groups.google.com/group/ninja-build/msg/b52e7d3b77bb... Most projects should probably not use Ninja. A previous iteration of the home page tried to scare users away. I could probably improve that.