commit | 27df5311c5ea2b5b5ae9132a5e60277b2a5982d4 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Mon Nov 09 13:39:14 2015 -0800 |
committer | Colin Cross <ccross@android.com> | Mon Nov 09 15:54:25 2015 -0800 |
tree | 65e7e8c11546697847935a3c3e491212199a6d06 | |
parent | 4e3b421f136299f6104d359605644756cc412a6c [diff] |
[C++] separate ninja shell script into two Separate the environment variables out of the ninja shell script so that the caller can source the environment script and then manually call ninja. Change-Id: If977a8316dceae955d71c32d528232d8b3f3aeef
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