| commit | 5ec1a7a66a5c66f0e4ba4999c5ac34f7022d246d | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Thu Jun 25 22:59:54 2020 -0700 |
| committer | Tianjie <xunchang@google.com> | Thu Jun 25 23:09:48 2020 -0700 |
| tree | 87abbfa0b52523f6c9222f6172c0aed867c20e61 | |
| parent | 0c263fd2717518c459d58c2c91e4c3ea87a94fa4 [diff] |
Rename the boot image for avb validation Starting from http://go/aog/1328118, we chained the 1st GKI boot image into vbmeta. However, this fails avb validation; because the avbtool constructs the image path based by using "partition name + ext". This cl works around the issue by renaming boot-5.4.img to boot.img, so avbtool can find the image correctly. Bug: 159656873 Test: run validate target file Change-Id: I577226596e139e5b5f3e6ca3c28ced02431ca392
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.