| commit | 706e16bee5f6b5fccd284476a9157ecc8c39f12c | [log] [tgz] |
|---|---|---|
| author | Brad King <brad.king@kitware.com> | Fri Feb 26 09:21:03 2021 -0500 |
| committer | Brad King <brad.king@kitware.com> | Fri Feb 26 10:31:27 2021 -0500 |
| tree | 78ae9af75529605ffc98631e9a8bd28e9c981b9d | |
| parent | 212cd97679e783de77230b009b23dd11344644ac [diff] |
Add tool to print code page information on Windows Since commit 00459e2b (Use UTF-8 on Windows 10 Version 1903, fix #1195, 2021-02-17), `ninja` does not always expect `build.ninja` to be encoded in the system's ANSI code page. The expected encoding now depends on how `ninja` is built and the version of Windows on which it is running. Add a `-t wincodepage` tool that generators can use to ask `ninja` what encoding it expects. Issue: #1195
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