| commit | b994524ea6b80d28ef613698d81136574f88c510 | [log] [tgz] |
|---|---|---|
| author | Pangyen Chen <pangyen.chen@mediatek.com> | Mon Jul 22 13:50:18 2019 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Mon Jul 22 18:04:03 2019 +0800 |
| tree | 77217f21f16ce2e074135e6aaf4c64c89939a9cd | |
| parent | 97f75df31cb16f7cb9c480ea08a63e43dde43a09 [diff] |
Inject boot patch level into boot-debug.img
When /boot partition is AVB chained, boot patch level will be
included into the AVB metadata appended to boot.img. We should
also do the same for boot-debug.img to pass keymaster v4 VTS
tests, whichs checks per-partition security patch levels are
indicated in AVB properties.
Bug: 136980825
Test: avbtool info_image --image $OUT/boot-debug.img, checks
com.android.build.boot.security_patch is there
Change-Id: I2ea1ebfa6abbbbc95639817c208a90642fc3d068
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.