commit | 59e7b3e05f1b8553f2c6e9fa329543d8b42fca8e | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Fri Jan 11 14:27:33 2019 -0800 |
committer | Dan Willemsen <dwillemsen@google.com> | Fri Jan 11 14:27:33 2019 -0800 |
tree | c2aeaac4f7064d6ba4dc02d4772d9a278449f10c | |
parent | 3173dc0bcf3faee24d3e173fdf9584f03eee1971 [diff] |
Use std::random_device instead of initializing via getpid getpid worked fine for this until we started trying to run Kati within a pid namespace (via nsjail). Then it consistently got the same pid, which resulted in multiple copies of Kati all running on the same CPU. Change-Id: If50846f742c3898ca92e21e0d2c78ad8e34d0128
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