commit | b741d1cfa9b880e2a872e266d2c411e9d93ac1c1 | [log] [tgz] |
---|---|---|
author | Calin Juravle <calin@google.com> | Wed Jan 23 18:06:06 2019 -0800 |
committer | Calin Juravle <calin@google.com> | Wed Jan 23 18:06:50 2019 -0800 |
tree | 04394152bc8ffb5035acd174abe1dd6cd4268ea7 | |
parent | e8f1a420bcc83e69b9ce6e51cfb3ec0c4b2007c5 [diff] |
Replace PRODUCT_BOOT_JARS with DEXPREOPT_BOOT_JARS_MODULES for nopreloads boot_profile_jars.zip is used to process the boot image profile (by filtering out data that does not belong to the boot classpath). We only need the jars that are actually preloaded, and not the ones which are updatable. Test: launch taimen_nopreload-userdebug; m Bug: 123313750 Change-Id: I630f78dda3d9b38aac04b0f364b25fbcda4e26a3
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.