| commit | 903a1ca7e17785ebca0a432d4554a6eb86ba73a8 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Thu May 07 17:32:10 2020 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Fri May 15 10:16:17 2020 -0700 |
| tree | 6d230d74879792a6128dc15ed6e1c09fcd4ff01c | |
| parent | 29beb858ef6df6fb5838d58c3da3f8dd90b1d853 [diff] |
support different boot partition sizes in aosp_arm64 The different boot images in aosp_arm64 have different partition size requirements. Add support for defining a partition size associated with each boot image variant. This support is limited to aosp_arm64 currently, which is built with recovery-as-boot. A previous version of this change did not update the boot-debug image AVB logic with the required macro for multiple boot partition size support. This is now required because the aosp-arm64 boot.img is configured as a chained AVB partition. Bug: 156036850 Bug: 155049180 Change-Id: I66b57de91042bfd56ba54a3659843d8cf7873955
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.