26b0a26e3e
When /boot partition is chained in AVB signing, libavb will try to read AVB footer from the end of /boot partition, even if the device is unlocked. However, this makes device unbootable when the unsigned boot-debug.img is flashed on /boot partition. This CL uses a test key from external/avb to sign the boot-debug.img if /boot partition is chained. Bug: 126493225 Bug: 129508966 Test: Enables chain partition for boot.img, `make bootimage_debug` then checks `avbtool info_image --image $OUT/boot-debug.img` Test: `make bootimage_debug-nodeps` Test: boot a device with a chained boot-debug.img Change-Id: I870cb70c70b7d4d7a30b77bed58cbca6e007d5e3 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
OWNERS | ||
README.md | ||
tapasHelp.sh | ||
Usage.txt |
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.