commit | 5f8a1fcd3335b45c1452e88b8ab87458757d212c | [log] [tgz] |
---|---|---|
author | David 'Digit' Turner <digit@google.com> | Mon Apr 17 11:44:44 2023 +0200 |
committer | David 'Digit' Turner <digit+github@google.com> | Thu Apr 27 18:33:59 2023 +0200 |
tree | a41fc5725ff1a91b414138e31657ddbb6411bf37 | |
parent | adf9bddd73869084a505fac83246e55c35880079 [diff] |
Allow duplicate rule variable usage. This fixes #1966 by removing the variable name from the lookups stack once the recursive lookup call has been performed. Without this, any previously expanded variable could no longer be referenced in the command, as Ninja would (incorrectly) complain about a cyclical dependency.
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