commit | b58bb4b2c8df6984ff64db21e8bbad928d2fd33e | [log] [tgz] |
---|---|---|
author | Shinichiro Hamaji <shinichiro.hamaji@gmail.com> | Thu Jul 30 18:02:51 2015 +0900 |
committer | Shinichiro Hamaji <shinichiro.hamaji@gmail.com> | Thu Jul 30 18:02:51 2015 +0900 |
tree | e31525eed580589f5f317b3626c5ccbac57f2b6b | |
parent | 09796efdf9ef64b77ddde7c6fc9d2fe41501e7d7 [diff] |
[C++] Re-generate build.ninja when ckati is updated
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.
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
% ~/src/kati/m2n -j10 % ./ninja.sh
Or
% ./ninja.sh -j10
Note the latter kills the parallelism of goma.