| commit | 8a7277df4127bd33dc0dd6f47d80d0591b95eb8d | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Wed Mar 23 18:13:42 2022 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Thu Mar 24 10:43:37 2022 -0700 |
| tree | 0a1ebba2999ff272c61913734aa6a15f6947d1ef | |
| parent | bc8d61f17b28dd0359dbcb0da474a45721ea53a5 [diff] |
Remove snapuserd from vendor ramdisk When BOARD_MOVE_RECOVERY_RESOURCES_TO_VENDOR_BOOT is set, snapuserd.recovery will be installed to vendor ramdisk, which we don't want. To remove snapuserd from vendor ramdisk, remove snapuserd.recovery. And only include it if dedicated recovery partition is enabled. For non-dedicated recovery case, boot partition contains snapuserd. Test: th Test: acloud create --local-image --local-instance, install OTA, reboot Change-Id: Ib8173f68a1f43b736fe609977a36ad4851e0c367
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.