commit | 0e205e11a6ebbc6eac90b1e7022f279946b71a6e | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Tue Oct 03 08:13:29 2017 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Oct 03 08:13:29 2017 +0000 |
tree | 598753e3856253062d073ec4da99be2085962612 | |
parent | 1fc74a3e9b55217719024c511512a2e7d572ae0e [diff] | |
parent | f8fc91dcc372c69c0667c73405ff57dc51982431 [diff] |
Snap for 4373608 from f8fc91dcc372c69c0667c73405ff57dc51982431 to pi-release Change-Id: Ie33639f1f0b5586f7f2c0831b4e718740c51d49a
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.
Now AOSP has kati and ninja, so all you have to do is
% export USE_NINJA=true
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 # Use --goma if you are a Googler. % ./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