commit | bfae8109797e2d90605ac28247259ecd6e0136fe | [log] [tgz] |
---|---|---|
author | Stefan Becker <[email protected]> | Wed Apr 27 11:40:09 2016 +0300 |
committer | Stefan Becker <[email protected]> | Wed Apr 27 12:15:14 2016 +0300 |
tree | a02c58246ab68730db4c160ca67ced63b28c7e3c | |
parent | a24a7a0e6574dc3ba618ba6a3b71a300bbbf7185 [diff] |
Remove test output in ckati_clean Fixes https://github.com/google/kati/issues/65 Change-Id: If1efb37f5d80ffe3f0972c6aa3090c39a0d96891
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