| commit | 626f6371dc267f65a46a724d90fef7c2fa488a8b | [log] [tgz] |
|---|---|---|
| author | Roshan Pius <rpius@google.com> | Wed Nov 27 09:31:34 2019 -0800 |
| committer | Roshan Pius <rpius@google.com> | Thu Nov 28 12:59:08 2019 +0000 |
| tree | 7747549c8dfcc92570640721faba54d1b2b25040 | |
| parent | fe283c99e6a1b663856aed96dd3bf25ac5960d99 [diff] |
base_system.mk: Align formatting for updatable boot jar variable Migrate PRODUCT_UPDATABLE_BOOT_MODULES & PRODUCT_UPDATABLE_BOOT_LOCATIONS to a new PRODUCT_UPDATABLE_BOOT_JARS. This new variable uses the same format as PRODUCT_UPDATABLE_SYSTEM_SERVER_JARS, i.e <apex>:<jar> pair. Test: Compiles & flashed device. Ensured that the bootclasspath & system_server class paths remain the same. Change-Id: I1cb26d5ec825cd1f5282a6e0255094ddf2fe046a
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.