| commit | 2abf159f9b3c8ee0f7a40cc657952424896722b5 | [log] [tgz] |
|---|---|---|
| author | Dan Willemsen <dwillemsen@google.com> | Mon Aug 26 23:25:17 2019 -0700 |
| committer | Dan Willemsen <dwillemsen@google.com> | Mon Aug 26 23:25:17 2019 -0700 |
| tree | d9dfef98ee38f7baec088d9f4381a18e931ad2d3 | |
| parent | 9de012ebde30eac4648f9163ae45f18d83336092 [diff] |
Improve performance (don't filter ALL_MODULES) It turns out that this single line was responsible for 28-44% of the time we spent parsing makefiles. So instead of filtering across $(ALL_MODULES), check to see if a variable that we always would set is set. Test: treehugger Test: check kati-build eval time before/after Change-Id: I946c2efd060181a4ae9edd3409c53d9b49a58285
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.