commit | bbc1455503c5819a0e170bf13ee324e5532dc4ad | [log] [tgz] |
---|---|---|
author | David 'Digit' Turner <digit@google.com> | Mon Apr 22 18:22:27 2024 +0200 |
committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 26 17:35:02 2024 +0000 |
tree | fae773ae3237fb4c63097803cc77bc96fc8800a0 | |
parent | b9c48103c2f40153380a84e1526d53c566132b5e [diff] |
Status: Use StatusTable to print pending commands. This makes it considerably easier to rebase out changes on top of upstream, and also benefits from a proper unit-test for StatusTable. Fuchsia-Topic: multiline-status Change-Id: Iba7374a4bc916f2e1c36d47bd20f4ab251fe614f Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/1037598 Reviewed-by: David Fang <fangism@google.com> Commit-Queue: David Turner <digit@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