commit | b9d63519c0ac0f6a83cade0f5656a2ee73e816ed | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Tue May 01 22:34:03 2018 -0700 |
committer | Dan Willemsen <dwillemsen@google.com> | Tue May 01 22:56:07 2018 -0700 |
tree | 28576f5f2b799f652841700db9cc443f4771f693 | |
parent | 60c664493242a1eeb7516f81682d54b94b27750d [diff] |
Use AndroidProducts.mk list from Soong's finder This saves ~300ms from get_build_var on our internal tree (1.3s -> 1.0s). On AOSP, it only saves ~60ms (0.60s -> 0.54s). It's also ran during lunch, and twice during every build (though the second time it was run with Kati's find emulator, which significantly reduces the overhead). Bug: 78020936 Test: diff out/.module_paths/AndroidProducts.mk.list with existing find results Change-Id: I195b2840854122e41275e24e886ca8c8cda13dac
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.