commit | 87b8da7af2c8bea28b1d8ab17679453d859f96e5 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Fri Oct 26 09:21:23 2018 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Fri Oct 26 09:27:37 2018 -0700 |
tree | 0c4a7b7081a2b351e5dc17a6cbc3a00433eee3b7 | |
parent | 4cc71ae464e38364f9f8abf3d2b79f1211c3b3ca [diff] |
Add --empty_ninja_file for test usecases In cases that we want to run Kati in many configurations to verify all of the generation logic works without errors, but don't care about running the final ninja file, writing it out only wastes time. So add a --empty_ninja_file option that skips writing out build rules and defaults information, leading to a very small ninja file. Our specific use case (Soong's build_test / multiproduct_kati) runs Kati several hundred times for different configurations, and the ninja files are around 750MB. Even when we truncate them immediately after writing, that still leads to hundreds of gigabytes of writes to disk. Change-Id: Ie4e7800ccfaeb653e89ed5d5ea3010b0c8ff314a
kati is an experimental GNU make clone. The main goal of this tool is to speed-up incremental build of Android.
Currently, kati does not offer a faster build by itself. It instead converts your Makefile to a ninja file.
For Android-N+, ckati and ninja is used automatically. There is a prebuilt checked in under prebuilts/build-tools that is used.
All Android's build commands (m, mmm, mmma, etc.) should just work.
Set up kati:
% cd ~/src % git clone https://github.com/google/kati % cd kati % make
Build Android:
% cd <android-directory> % source build/envsetup.sh % lunch <your-choice> % ~/src/kati/m2n --kati_stats % ./ninja.sh
You need ninja in your $PATH.
% ./ninja.sh -t clean
Note ./ninja.sh passes all parameters to ninja.
For example, the following is equivalent to "make cts":
% ./ninja.sh cts
Or, if you know the path you want, you can do:
% ./ninja.sh out/host/linux-x86/bin/adb