91964c82e3
builds (reland). - Use art/build/boot/boot-image-profile.txt for the primary boot image in the ART module, both when it's built from source in platform and as an unbundled module. - Use frameworks/base/boot/boot-image-profile.txt for the framework extension image in platform, but not in unbundled builds. This should obsolete the combined profile frameworks/base/config/boot-image-profile.txt. This relands https://r.android.com/1881863 with a fix to allow multiple values on PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION. Test: build/soong/soong_ui.bash --dumpvar-mode \ PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION and check that it prints both art/build/boot/boot-image-profile.txt and frameworks/base/boot/boot-image-profile.txt in a platform build on master. Test: build/soong/soong_ui.bash --dumpvar-mode \ PRODUCT_DEX_PREOPT_BOOT_IMAGE_PROFILE_LOCATION and check that it prints only art/build/boot/boot-image-profile.txt in an unbundled build on master-art. Test: banchan com.android.art && m on master-art and check that out/soong/.intermediates/art/build/apex/com.android.art/android_common_com.android.art_image/image.apex/javalib/x86_64/boot.oat shrinks from 14 MB to 4.7. Test: m droid on master together with https://r.android.com/1895131 and check that out/soong/.intermediates/art/build/apex/com.android.art/android_common_com.android.art_image/image.apex/javalib/x86_64/boot.oat and out/target/product/vsoc_x86_64/system/framework/x86_64/boot-framework.oat are identical. Test: lunch armv8-eng && art/tools/buildbot-build.sh on master-art Bug: 174746397 Change-Id: I9114271bc69cf0888150b2c778a086bc50b73045
Android Make Build System
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.