| commit | 03230250a3773136eb6b992340405fe619e91620 | [log] [tgz] |
|---|---|---|
| author | Lucas Wei <lucaswei@google.com> | Mon Apr 18 16:00:40 2022 +0800 |
| committer | Lucas Wei <lucaswei@google.com> | Thu Apr 21 00:27:27 2022 +0800 |
| tree | 32296add8df5c7dfc45c59e8629da7f20fdd3d9a | |
| parent | 6337ed39e1397244428efdc94fe8ab1cd32356ab [diff] |
vendor_kernel_boot: Update releasetools for vendor_kernel_boot add_img_to_target_files.py will re-make image and build a new signed vbmeta.img with new images in target-file. We need to add vendor_kernel_boot into AVB signing list and make it support that image. Test: make dist -j110 and check vbmeta.img Bug: 214409109 Signed-off-by: Lucas Wei <lucaswei@google.com> Change-Id: Id07433f3dc33f95e2edd49de890f1e098cb9ef31
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.