commit | bfb2ee8039218dcc7dc6f2942419afad3a7401a1 | [log] [tgz] |
---|---|---|
author | David 'Digit' Turner <digit@google.com> | Wed Apr 19 18:57:11 2023 +0200 |
committer | David 'Digit' Turner <digit@google.com> | Fri Apr 21 19:28:21 2023 +0200 |
tree | a4b780a5eb8af8c3aec9ed4a3b157689fef3f06d | |
parent | d867a3b87b096418bb278fb884c932fe4373fc58 [diff] |
Enable ppoll() usage when available. This patch modifies the CMakeLists.txt file to probe for ppoll() on the target system, and define -DUSE_PPOLL=1 if it is available. This matches the default behavior of the configure.py script. Note that there is no noticeable performance difference before build commands are launched, so this change is very hard to benchmark properly. Fix for https://github.com/ninja-build/ninja/issues/1821 Upstream-Pull-Request: https://github.com/ninja-build/ninja/pull/2290 Change-Id: I19bd5f1a933477426da70025532e8613c67cd7af
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