3941a876de
On legacy devices (launched with R and below), if device: - has a vendor_boot partition, and - uses recovery_as_boot Then, when building the recovery/boot partition, the device-specific bits, including dtb/kernel base/pagesize should be moved to vendor_boot. Previously, it is incorrectly assumed that A/B => recovery_as_boot. In reality, we do have A/B devices with a dedicated recovery partition. Note that for devices that uses GKI (BOARD_USES_GENERIC_KERNEL_IMAGE), recovery_as_boot is never set to true. Instead, recovery resources are moved to vendor_boot. On these devices, the conditional 'vendor_boot && recovery-as-boot' is always false. Hence: - If the device has a dedicated recovery partition, it should use V3 header, and dtb/base/pagesize won't be in recovery header. - If device does not have a dedicated recovery partition, the recovery image won't be built. Test: builds Change-Id: I0db2af20470cbe8a21044a984cccf264590aaccf
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.