StatusPrinter: Display pending commands in smart terminals. When NINJA_STATUS_MAX_COMMANDS is set in the environment to a decimal value that is > 0, then display under the status line the list of oldest running edges, with their elapsed time. For example, with a value of 4 in a Fuchsia checkout this looks like the following (manual truncation to keep this readable as a commit message): ``` ninja: Entering directory `out/default' [5009/25019](34) STAMP fidling/obj/sdk/fidl/f... 2.5s | CXX obj/BUILD_DIR/gen/src/lib/fostr/... 2.2s | CXX obj/src/developer/forensics/cras... 2.1s | CXX obj/src/lib/intl/time_zone_info/... 2.0s | RUST obj/src/connectivity/wlan/wlanc... ``` The refresh period can be set with NINJA_STATUS_REFRESH_MILLIS and defaults to 100 (i.e. 10 times per second). BYPASS_INCLUSE_LANGUAGE_REASON=dumb_terminal_is_exactly_the_terminology_used_by_upstream_project Fuchsia-Topic: multi-line-status Original-Change-Id: I90f2f1bba62d6364d5474145cdcfa4df8d1f214e Change-Id: I93e80a42c1b65746ea6ef36507d4601c13ca2af6 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/1071422 Reviewed-by: David Fang <fangism@google.com>
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.
You can either build Ninja via the custom generator script written in Python or via CMake. For more details see the wiki.
./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.:
./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 -Bbuild-cmake 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:
./build-cmake/ninja_test
You must have asciidoc and xsltproc in your PATH, then do:
./configure.py ninja manual doc/manual.pdf
Which will generate doc/manual.html.
To generate the PDF version of the manual, you must have dblatext in your PATH then do:
./configure.py # only if you didn't do it previously. ninja doc/manual.pdf
Which will generate doc/manual.pdf.
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.
./configure.py # if needed ninja doxygen
Then open doc/doxygen/html/index.html in a browser to look at it.