ikifof 714621dba1 Adding a way to clean dead build artifacts that have an entry in the build log,
but are no longer produced by the current manifest. For now adding a dedicated
"-t cleandead" option, since it should be run after reading the log; ideally
it should be part of the build config and done before to start looking for
dirty targets so that an incremental build would produce the same end result
as a clean build from scratch. But since I am not 100% sure to understand the
comment in the NinjaMain::isPathDead(), I opted to make it a tool for now to
avoid impacting users who want to keep those files.
The option name "cleandead" was selected insteadof something like "reap" to
keep the "clean" prefix.
2019-05-25 11:14:43 -07:00
2019-05-09 16:36:47 +02:00
2014-04-15 22:08:21 -07:00
2019-05-10 17:05:07 +02:00
2018-11-02 10:46:42 +01:00
2014-11-18 08:15:37 -08:00
2015-11-19 12:41:32 -08:00
2017-09-19 10:30:35 +09:00

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

See the manual -- https://ninja-build.org/manual.html or
doc/manual.asciidoc included in the distribution -- for background
and more details.

Binaries for Linux, Mac, and Windows are available at
  https://github.com/ninja-build/ninja/releases
Run './ninja -h' for Ninja help.

To build your own binary, on many platforms it should be sufficient to
just run `./configure.py --bootstrap`; for more details see HACKING.md.
(Also read that before making changes to Ninja, as it has advice.)

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 HACKING.md first.
Description
a small build system with a focus on speed
Readme 4.7 MiB
Languages
C++ 87.8%
Python 7.5%
C 2.5%
CMake 0.9%
Shell 0.6%
Other 0.7%