| commit | c9ec59c72a1fe9a0b1ee0d5b064f298dca1da150 | [log] [tgz] |
|---|---|---|
| author | Ulya Trafimovich <skvadrik@google.com> | Thu Nov 25 12:41:47 2021 +0000 |
| committer | Ulya Trafimovich <skvadrik@google.com> | Fri Nov 26 16:02:54 2021 +0000 |
| tree | 66ff630e6e74efc4ea610143e02a50f0dcc872fb | |
| parent | 00496c1683bb6ee2070e2633c52e23043c7644ea [diff] |
Sort PRODUCT_APEX_BOOT_JARS automatically. This is a follow-up CL for https://r.android.com/1900565. This is needed because product makefiles may need to add their own APEX boot jars, and they cannot insert them in the correct alphabetical order on the list. So it needs to be sorted automatically. Do this after processing all product makefiles and populating the variable, but before passing it to Soong. Bug: 207474880 Test: lunch aosp_cf_x86_64_phone-userdebug && launch_cvd # cuttlefish device boots successfully Change-Id: I86b58ef8aeac595e401d872f59a2936a67bedeec
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.