| commit | ceaa411fcb6cd77bd51b365aa3decc8f1559348c | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Tue Jan 19 13:55:42 2021 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Tue Jan 19 17:07:45 2021 +0800 |
| tree | bbd2413238ab32a32e3515e5e99e88830a5aacd5 | |
| parent | fc596c996f35e123a0c2430894500aae97b5fde7 [diff] |
Includes recovery resources into vendor_boot-debug.img Commit I56dda56bab7def1540f4fb506323e3e605620cd4 adds BOARD_MOVE_RECOVERY_RESOURCES_TO_VENDOR_BOOT and includes $(TARGET_RECOVERY_ROOT_OUT) directory when building vendor ramdisk if BOARD_MOVE_RECOVERY_RESOURCES_TO_VENDOR_BOOT is set. We should do the same thing when building the vendor debug ramdisk as well. Otherwise, lacking some recovery files makes the device unable to boot into fastbootd/recovery mode. Bug: 177712689 Test: `make vendorbootimage_debug`, then unpack ./obj/PACKAGING/vendor-boot-debug_intermediates/vendor-ramdisk-debug.cpio.lz4 to check it includes recovery resources via: `lz4 -d -c ../vendor-ramdisk-debug.cpio.lz4 | cpio -idm` Test: device can boot into fastbootd after flashing vendor_boot-debug.img Change-Id: I4744c6600866436ed7d5a321e67e20b8f3da8a81
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.