| commit | b51a3e83ff25ca95464b179344cfe4a98e242a21 | [log] [tgz] |
|---|---|---|
| author | John Drouhard <john@jmdtech.org> | Tue Mar 23 15:10:43 2021 -0500 |
| committer | John Drouhard <john@jmdtech.org> | Wed Mar 24 08:49:58 2021 -0500 |
| tree | 4115d9d0fbdfcdfb2c0c6ec233b0b919362da876 | |
| parent | db6c4ac47601c88984822e1e7b5f4b9044dd6d81 [diff] |
Revert "Change build log to always log the most recent input mtime" This reverts commit 67fbbeeec91ec171da7d4e297b8f9b319f3424c8. There were a few missing test cases exposed by CMake's test suite that need slight adjustments. Better to revert the original attempt, add the test cases, and then re-land the change with the fixes. Fixes #1932
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 -H. 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