commit | b0b26cc9c43eb6a3ba728a8bfbcbceeb6dfcab20 | [log] [tgz] |
---|---|---|
author | Jan Niklas Hasse <jhasse@bixense.com> | Wed Aug 26 12:07:25 2020 +0200 |
committer | Jan Niklas Hasse <jhasse@bixense.com> | Wed Aug 26 12:12:30 2020 +0200 |
tree | 74603a7a70943ae30022896bf3f742a711a3d3ee | |
parent | 9ddd3c917793bb97eb19d571429cdedf07501c03 [diff] |
Close BuildLog while running generators, fix #1724 While #1780 delayed opening .ninja_log until the first write, this this didn't fully fix the issue on Windows: There might be build statements which run before the generator resulting in an actual write to .ninja_log. To fix this once and for all the BuildLog now gets closed before running the generator. BuildLog::log_file_path_ won't be cleared so that it can be opened again after the generator finished.
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