commit | 003bb3b32f6f42c45f9eb51881a52ee2c370b522 | [log] [tgz] |
---|---|---|
author | Dylan Baker <dylan@pnwbakers.com> | Fri Mar 29 13:32:37 2024 -0700 |
committer | Dylan Baker <dylan@pnwbakers.com> | Tue Apr 02 11:52:18 2024 -0700 |
tree | 899f9358b851f015952875ab0bcc3612784797ce | |
parent | 36843d387cb0621c1a288179af223d4f1410be73 [diff] |
cleandead: remove outputs specified by dyndep files Load this information before cleaning, as the normal `clean` operation does. This was accidentally missed when commit 714621db (Adding a way to clean dead build artifacts ..., 2018-04-27, v1.10.0~1^2~9^2~1) was rebased after the normal `clean` operation was updated by commit a3cbb4d (clean: remove outputs specified by dyndep files, 2019-02-12, v1.10.0~1^2~53^2~4). This fixes a bug causing artifacts to be spuriously flagged as "dead" and erased.
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