be0b6cee4f
Kati's find emulator doesn't understand "| sort", so use use the make function instead so that we can emulate the find commands. before: *kati*: shell time (regen): 1.316989 / 187 after: *kati*: shell time (regen): 1.249748 / 184 The time has a lot of variance, the important change is the reduction in number of shell commands. Kati has other issues with some of these (it doesn't support find's implicit -a), which is why it only goes down by 3. I'll be fixing Kati separately to handle those cases. Test: diff out/build-aosp_taimen.ninja before&after Change-Id: I5c8c2993f01a8a6af84963e903a8a0c186a61e82 |
||
---|---|---|
core | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.mk | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
OWNERS | ||
README.md | ||
tapasHelp.sh | ||
Usage.txt |
Android Make Build System
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.