| commit | 3a820dd5a0aa6612fc0dbacfee662b17cce22dd5 | [log] [tgz] |
|---|---|---|
| author | Bob Badour <bbadour@google.com> | Tue Dec 07 15:35:07 2021 -0800 |
| committer | Bob Badour <bbadour@google.com> | Tue Dec 07 15:36:10 2021 -0800 |
| tree | bf05b6b57a8f2f66a90d688882d46ab03c885ece | |
| parent | 1295bc51383913eddfa76fb2f9c6e22cac102a4b [diff] |
license metadata performance Tune the top-down walk to avoid needlessly walking the same subtree over and over again with the same condition(s). Takes walking system image down from 3m to 1.5s. Test: m all systemlicense listshare checkshare dumpgraph dumpresolutions Bug: 68860345 Bug: 151177513 Bug: 151953481 Change-Id: I4354800cd8dfc42efd4df274d2ce45eaa3e0a99f
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.