| commit | f802a95cbbcfe41587f78ecc75a40492a7810666 | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit+github@google.com> | Wed Sep 11 18:32:23 2024 +0200 |
| committer | David 'Digit' Turner <digit@google.com> | Tue Oct 01 16:38:19 2024 +0000 |
| tree | be5f67e9b09a81bb42e5f045769c65f34e6cd309 | |
| parent | b23e3858e5eabaad1b7f7a1fa1c2e5934b8ff7b4 [diff] |
Add misc/jobserver_pool.py This implements a GNU jobserver token pool that will be used for testing the upcoming jobserver Ninja client implementation. Note that the implementation is basic and doesn't try to deal with broken protocol clients (which release more tokens than they acquired). Supporting them would require something vastly more complex that would monitor the state of the pipe/fifo at all times. NOTE: This is the first in a series of several CLs to implement jobserver support in Ninja, both client and server modes. A corresponding PR has been submitted upstream as PR#2506 but will likely take weeks before being accepted, so landing this in our tree makes the feature available earlier for Fuchsia builds. Fuchsia-Topic: jobserver-support Change-Id: I73ba252d7fd9708c752dfa6871c1b09432b62ac2
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.
If you have a GoogleTest source directory, you can build the tests by passing its path with --gtest-source-dir=PATH option, or the GTEST_SOURCE_DIR environment variable, e.g.:
./configure.py --bootstrap --gtest-source-dir=/path/to/googletest ./ninja all # build ninja_test and other auxiliary binaries ./ninja_test` # run the unit-test suite.
Use the CMake build below if you want to use a preinstalled binary version of the library.
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.