commit | 086a9b2f8833fd45f2119596f74f90b9f7e2cdf5 | [log] [tgz] |
---|---|---|
author | David Callu <callu.david@gmail.com> | Thu Jul 16 14:06:20 2020 +0200 |
committer | Jan Niklas Hasse <jhasse@bixense.com> | Fri Jul 17 09:56:32 2020 +0200 |
tree | 57d637a73fa5a32c20d946d5bbbb8cd08492ffbd | |
parent | 6c5e886aacd98766fe43539c2c8ae7f3ca2af2aa [diff] |
cmake: use PROJECT_{SOURCE,BINARY}_DIR instead of CMAKE_{SOURCE,BINARY}_DIR CMAKE_SOURCE_DIR refer to the full path to the top level of the current CMake source tree PROJECT_SOURCE_DIR refer to the source directory of the last call to the project() command made in the current directory scope or one of its parents when ninja is use as a subproject, the build fail because of this.
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