| commit | 4e281f5fe13c75389e3972251bb9ff68894e838b | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@google.com> | Wed Aug 09 16:58:21 2023 +0200 |
| committer | David Turner <digit@google.com> | Fri Aug 18 07:46:54 2023 +0000 |
| tree | 8ee8b138407eb93015c0f77ada1b897cdcf8749a | |
| parent | 506677e7423d7c1c2be8e1c6b99c1ae30e759df9 [diff] |
Move StatusPrinter environment variables to BuildConfig The values are now part of BuildConfig, which will allow sending them to a remote server in the future. Fuchsia-Topic: persistent-mode Change-Id: I071b68ffb39d89120bc93db0e2bf4fc7bc8a3230 Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/899658 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.
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