| commit | ee758131624170b9083a324de53c4afd79320531 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Jan 06 13:25:22 2020 +0900 |
| committer | Anton Hansson <hansson@google.com> | Fri Jan 10 15:15:47 2020 +0000 |
| tree | a0b94e192113c0abff79a63e4507f68cc684eab1 | |
| parent | c30b734f427915ecc92677017b71d6e005d806bf [diff] |
Correctly gather boot jars from APEXes Jars in APEXes have Make module names <jar_name>.<apex_name>. e.g. updatable-apex.com.android.media. Previously, we have used <jar_name> which actually meant the platform variant of the jar. This is not only incorrect, but also is causing problem as the platform variant is no longer available when the jar is configured to be available only for the corresponding APEX (via the apex_available property). Fixing the problem by correctly using <jar_name>.<apex_name> scheme. Bug: N/A Test: m Change-Id: I6e255ce88c9bd80120b29197fb2637a64010f531 Merged-In: I6e255ce88c9bd80120b29197fb2637a64010f531
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.