| commit | 1908f9731922501a8fc58b00e463676d1ce0b9e1 | [log] [tgz] |
|---|---|---|
| author | Roopesh Nataraja <roopeshr@quicinc.com> | Mon Jun 08 19:54:13 2020 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Mon Jun 15 17:10:56 2020 -0700 |
| tree | e0e3cc5ac3992900e7cef2480e9b19b26ee72a03 | |
| parent | 2e2cb808cb1959b6eb76892bc68f3050f3d92978 [diff] |
Include image descriptor of only the first boot image in vbmeta
Multiple boot images can be generated based on BOARD_KERNEL_BINARIES
but vbmeta would capture the image descriptor of only the first boot
image specified in BUILT_BOOTIMAGE_TARGET.
Bug : 158213759
Test: Compile multiple boot images and check if vbmeta.img
includes image descriptor of only the first boot image
specified in BUILT_BOOTIMAGE_TARGET
Change-Id: Ib70f65d98546a436da82656bc5c911d437618bb5
Merged-In: Ib70f65d98546a436da82656bc5c911d437618bb5
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.