c5ec8e95bc
It turns out we have a few tests with thousands of test data files, which this logic does not handle very well. Just switching from `x := $(x) ...` to `x += ...` accomplishes the majority of these gains, but I rewrote the logic to be less function-call+eval based to hopefully make it easier to understand. For an aosp-master/aosp_coral-eng build, this brings the time spent in this logic from 7.6s to 0.3s (total kati runtime of 54s to 46s). Kati's peak memory use (maxrss) also shrunk from 6.1GB to 3.8GB. Bug: 158488548 Test: build-aosp_coral.ninja is the same before/after Change-Id: Ia2ec8b29b5c1dd12fa7ea10b4f80fe802c692725 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
OWNERS | ||
rbesetup.sh | ||
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.