| commit | 9425daba0c7f833ff661755964f83ad4686140e0 | [log] [tgz] |
|---|---|---|
| author | satayev <satayev@google.com> | Wed Apr 28 13:27:33 2021 +0100 |
| committer | satayev <satayev@google.com> | Wed May 05 11:05:59 2021 +0100 |
| tree | 57debcfa68fc0ad161e2e67f098f431f3f91f9ae | |
| parent | f00b7aa36129d4bbb67891f8e45716e92b5a372d [diff] |
Sort PRODUCT_UPDATABLE_BOOT_JARS. At runtime it is now responsibility of derive_classpath to define value of BOOTCLASSPATH. As we are modularizing BCP configs, the end goal is to have a following ordering: - ART APEX jars - /system jars - /system_ext jars - /apex jars from non-updatable apexes - /apex jars from updatable apexes Note that /apex configs are sorted alphabetically, however they preserve relative ordering of the jars exported from individual apexes. For example, core-oj.jar would come before bouncycastle.jar if ART apex defines their relative order as such. To match end goal expectations of the APEX ordering, sort existing list of PRODUCT_UPDATABLE_BOOT_JARS. Bug: 180105615 Test: presubmit Change-Id: I15512c0da79ad94b547325d563dac473c006f9fd
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.