| commit | 4c69c2ff7256b97cbea3f9bd3298b1aafde12ec0 | [log] [tgz] |
|---|---|---|
| author | Ulya Trafimovich <skvadrik@google.com> | Thu Apr 30 10:59:48 2020 +0100 |
| committer | Ulya Trafimovich <skvadrik@google.com> | Thu Apr 30 17:16:29 2020 +0100 |
| tree | 8b8a630b9843726b039a2ff2093d661e514601cd | |
| parent | a9800b4db5d377a5c2208cc546601a66c46407d2 [diff] |
Use two-column format for PRODUCT_BOOT_JARS components. The first component is the apex name, or a special name "platform" if the boot jar is a platform jar rather than a part of some apex. This is a prerequisite change for moving core-icu4j to a separate com.android.i18n apex. Old one-column format is still supported, but all unqualified components of PRODUCT_BOOT_JARS get "platform:" prepended to them after reading the product makefiles. Test: aosp_walleye-userdebug boots Bug: 138994281 Change-Id: I0f79c7d10477880ca65354251a5d1ca0b7ce79ab
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.