| commit | aba5c9eacd54e9b0cf5fbeaa1157ca8ec1d00786 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Mon Sep 27 14:08:41 2021 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Mon Sep 27 14:11:14 2021 +0800 |
| tree | dbb90d2cfe4f468432e057c5440186cad4b86a89 | |
| parent | a2a5db44663a8dff93f0456034e17848155613f8 [diff] |
Fix aosp_x86_64-user build failure Commit Ia982eb2ee3d1eb64db72c1836e433bcc53e71e3f removes boot-5.4.img and leaves only a boot-5.10.img file, which makes 'boot_container' become false. This leads to the failure in AddVbmetaDigest() as it will search a 'boot.img' based on the 'boot' descriptor from the vbmeta.img. Add a condition that if boot_images[0] is not 'boot.img' then the build is also a boot container. Bug: 199807830 Test: build aosp_x86_64-user Change-Id: I4a9487b075186f0abf2ba74d3a1cf78072352a05
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.