commit | 97944c71dceea5e84272f8951b6d464b728de18a | [log] [tgz] |
---|---|---|
author | chunhui dai <chunhuid@amazon.com> | Fri Jun 21 16:45:47 2024 +0000 |
committer | chunhui dai <chunhuid@amazon.com> | Fri Jun 21 17:01:27 2024 +0000 |
tree | 6c9fe4b51c227a0dcc80adb02426d6013b525da7 | |
parent | 79d04e41154a3abf272251af6fc9814c40ebd556 [diff] |
Add macro to support prebuilt vendor_vboot.img There are marcos support to link prebuilt images and generate AVB images in "make"/"make dist" flow. Currently defined marcos only cover boot.img /init_boot.img/vendor.img and so on, missing the vendor_boot.img. Appending a marco for prebuilt vendor_boot.img to work like other prebuilt images. Test: manual Build pass in "make" and "make dist" flow and boot up with AVB Change-Id: I7b296f82e57e8f71a0757d872d35ac27a8d2ecbe Signed-off-by: chunhui dai <chunhuid@amazon.com>
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.