| commit | 7fdd96a48def7f0d7909d045ce8afffb4d04ebbc | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@google.com> | Tue Dec 12 16:53:46 2023 +0100 |
| committer | David Turner <digit@google.com> | Wed Dec 13 15:47:31 2023 +0000 |
| tree | 3ab350d302f76462ad8d4f512e9d069d295ce336 | |
| parent | 57814db5fd5f01cf115b1926376e830a0c18e9c7 [diff] |
Status: properly handle changes in TERM and CLIFORCE_COLOR During incremental builds, the values of TERM and CLIFORCE_COLOR were not updated from the client environment, which resulted in incorrect behavior, which could be seen by doing the following: ``` export NINJA_PERSISTENT_MODE=1 export NINJA_STATUS_MAX_COMMANDS=8 ninja -C out emacs ``` The root of the problem was that emacs sends an interactive tty to the compile command, but sets TERM to the special "dumb" value that Ninja interprets to disable "smart terminal" mode. This TERM update was not seen by Ninja which thought it was running in a smart terminal session. This CL fixes the situation by adding the LinePrinter::Reset() method which takes the values of the TERM and CLIFORCE_COLOR environment variables, and calling it from the Status constructor. Fuchsia-Topic: persistent-mode Change-Id: I1ec2af5c36e1e7f9b91cc81c7e14ffc3bfb9e08d Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/959596 Reviewed-by: David Fang <fangism@google.com>
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