          MODULE=ninja
         VERSION=1.13.2
          SOURCE=$MODULE-$VERSION.tar.gz
 SOURCE_URL_FULL=https://github.com/ninja-build/ninja/archive/refs/tags/v$VERSION.tar.gz
      SOURCE_VFY=sha256:974d6b2f4eeefa25625d34da3cb36bdcebe7fbce40f4c16ac0835fd1c0cbae17
        WEB_SITE=https://ninja-build.org/
         ENTERED=20141002
         UPDATED=20251121
           SHORT="A small build system with a focus on speed"

cat << EOF
Ninja is a small build system with a focus on speed. It differs from other build systems in two major
respects: it is designed to have its input files generated by a higher-level build system, and it is
designed to run builds as fast as possible.

Why yet another build system?
Where other build systems are high-level languages Ninja aims to be an assembler.

Ninja build files are human-readable but not especially convenient to write by hand. (See the generated
build file used to build Ninja itself.) These constrained build files allow Ninja to evaluate incremental
builds quickly. For the Chrome browser on Linux (the motivating project behind Ninja), Ninja is under a
second for a no-op build where the equivalent Makefiles took over ten seconds.

Ninja's low-level approach makes it perfect for embedding into more featureful build systems. Via gyp it can
build Chrome and v8 and node.js etc.; via CMake it can build LLVM and KDE and Blender etc.
EOF
