commit | c7b2cf60f4c07440728307c0e68f99c464ac7f7b | [log] [tgz] |
---|---|---|
author | Hans Wennborg <hans@chromium.org> | Fri Jun 25 13:59:34 2021 +0200 |
committer | Hans Wennborg <hans@chromium.org> | Fri Jun 25 14:41:24 2021 +0200 |
tree | d234b6f38dcc1eea40b5ba918500318f057da9db | |
parent | d68f107f7a80d552d764c8cd0545955be02debe2 [diff] |
CLParser: Don't filter filename lines after seeing /showIncludes The /showIncludes output always comes after cl.exe echos the filename, so there is no need to filter out filename lines afterwards. This makes it less likely that CLParser will "over filter" the compiler output. For example, using the -H flag with clang-cl may lead to output lines ending in .cc, which are not supposed to be filtered out.
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