| commit | c7da3e64f97ef61f9201eff7ad70a8a652f506bb | [log] [tgz] |
|---|---|---|
| author | Arthur Milchior <arthur@milchior.fr> | Sun Nov 07 18:00:27 2021 +0100 |
| committer | Arthur Milchior <arthur@milchior.fr> | Sun Nov 07 18:00:27 2021 +0100 |
| tree | 73dd005beae6be3db383fb14abe662b0ebb8c48f | |
| parent | 0cd88287a4cd77d11c92c7a9b44bb15fb787a1ee [diff] |
NF: clarify documentation's part about rules description The word "eventually" was quite strange here and should probably removed. I suspect "potentially" was meant (which in French is "eventuellement", a standard false friend). In any way, after a quick look at the source/ninja message, I chose to even clarify this part of the doc, indicating that the `-d` option is required here.
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 at 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