ninja Documentation

A small build system with a focus on speed

13,312 stars C++ C++ 2 files ยท ~940 tokens
RAW Doc

Technical Documentation: ninja-build/ninja

โ„น๏ธ Provenance: Multi-Tier Ingestion ยท CodeWiki Reference

Overview (`README.md`)

Ninja

Ninja is a small build system with a focus on speed.
https://ninja-build.org/

See the manual or
doc/manual.asciidoc included in the distribution for background
and more details.

Binaries for Linux, Mac and Windows are available on
GitHub.
Run ./ninja -h for Ninja help.

Installation is not necessary because the only required file is the
resulting ninja binary. However, to enable features like Bash
completion and Emacs and Vim editing modes, some files in misc/ must be
copied to appropriate locations.

If you're interested in making changes to Ninja, read
CONTRIBUTING.md first.

Building Ninja itself

You can either build Ninja via the custom generator script written in Python or
via CMake. For more details see
the wiki.

Python

text
./configure.py --bootstrap

This will generate the ninja binary and a build.ninja file you can now use
to build Ninja with itself.

If you have a GoogleTest source directory, you can build the tests
by passing its path with --gtest-source-dir=PATH option, or the
GTEST_SOURCE_DIR environment variable, e.g.:

sh
./configure.py --bootstrap --gtest-source-dir=/path/to/googletest
./ninja all     # build ninja_test and other auxiliary binaries
./ninja_test    # run the unit-test suite.

Use the CMake build below if you want to use a preinstalled binary
version of the library.

CMake

To build the ninja binary without building the unit tests, disable test building
by setting BUILD_TESTING to OFF:

text
cmake -Bbuild-cmake -DBUILD_TESTING=OFF
cmake --build build-cmake

The ninja binary will now be inside the build-cmake directory (you can
choose any other name you like).

To run the unit tests, omit the -DBUILD_TESTING=OFF option, and after
building, run:

text
build-cmake/ninja_test

Generating documentation

Ninja Manual

You must have asciidoc and xsltproc in your PATH, then do:

text
./configure.py
ninja manual doc/manual.html

Which will generate doc/manual.html.

To generate the PDF version of the manual, you must have dblatext in your PATH
then do:

sh
./configure.py    # only if you didn't do it previously.
ninja doc/manual.pdf

Which will generate doc/manual.pdf.

Doxygen documentation

If you have doxygen installed, you can build documentation extracted from C++
declarations and comments to help you navigate the code. Note that Ninja is a
standalone executable, not a library, so there is no public API, all details
exposed here are internal.

sh
./configure.py   # if needed
ninja doxygen

Then open doc/doxygen/html/index.html in a browser to look at it.


Overview (`doc/README.md`)

This directory contains the Ninja manual and support files used in
building it. Here's a brief overview of how it works.

The source text, manual.asciidoc, is written in the AsciiDoc format.
AsciiDoc can generate HTML but it doesn't look great; instead, we use
AsciiDoc to generate the Docbook XML format and then provide our own
Docbook XSL tweaks to produce HTML from that.

In theory using AsciiDoc and DocBook allows us to produce nice PDF
documentation etc. In reality it's not clear anyone wants that, but the
build rules are in place to generate it if you install dblatex.


--- METRICS ---