| commit | 8e6c741a4b6c4f5cab4695016be2b0a8183bab83 | [log] [tgz] |
|---|---|---|
| author | David Röthlisberger <david@stb-tester.com> | Thu Jan 06 12:44:27 2022 +0000 |
| committer | David Röthlisberger <david@stb-tester.com> | Wed May 08 13:44:50 2024 +0100 |
| tree | 3cb973223340aee26aa37aecec1662b9c701641b | |
| parent | 554579d1204cd8430f18d25de4848b152f9a4136 [diff] |
"explain" debug prints just before each command is run The explanations are printed just before each command is run. Before, it would potentially print pages & pages of explanations at the beginning, and it was hard to tell which explanation caused a particular command to run. Edges that are pruned due to "restat" used to print all their explanations at the beginning, cluttering up the output with explanations that didn't actually cause any rebuilding. Now, those explanations aren't printed if those edges aren't run.
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
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.