| commit | 09e9471eac40ddadc5996a2b6a90db274fd4be77 | [log] [tgz] |
|---|---|---|
| author | satayev <satayev@google.com> | Tue Jun 15 11:35:40 2021 +0100 |
| committer | satayev <satayev@google.com> | Fri Jul 16 14:50:29 2021 +0100 |
| tree | 0a781e961fb2fd5a1e7197755c946802bdd23ff1 | |
| parent | 1b00d58d93208023b8aa2f793597092820b9d0fc [diff] |
Move core-icu4j to PRODUCT_UPDATABLE_BOOT_JARS. ... but not really: move it back to PRODUCT_BOOT_JARS before the list is passed to soong. This ensures that core-icu4j remains on the boot image for system health reasons and maintains the status quo. core-icu4j is the only APEX jar (aside from ART jars) that is ever meant to be part of the boot image. This is an implementation detail that most devs don't and shouldn't care about. Instead, most devs assume that PRODUCT_UPDATABLE_BOOT_JARS is where all apex jars are meant to go. In the follow ups, PRODUCT_UPDATABLE_BOOT_JARS would be renamed to PRODUCT_APEX_BOOT_JARS, regardless of the updatable property. This also solves the problem where vendors add /system and /system_ext boot jars to PRODUCT_BOOT_JARS outside of default_art_config.mk and essentially violate the ordering requirement: all /apex jars come after /system and /system_ext. Bug: 191127295 Test: atest CtsClasspathsTestCases derive_classpath_test Change-Id: Ifdfdd02519a0f5baea45619523f0c1eb8be186bc
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.