| commit | 047ff459043a42f10e404fc7cb54a7be0903d53f | [log] [tgz] |
|---|---|---|
| author | Ricky Cheung <rcheung844@gmail.com> | Fri Mar 29 18:55:05 2024 +0800 |
| committer | LuK1337 <priv.luk@gmail.com> | Sat Oct 19 00:16:02 2024 +0200 |
| tree | 06685bff65b9cc7be0bc3ed47b028b8841cb684d | |
| parent | 1e44b0894e4d6affa360ce2e2503a8db1ad3c9d1 [diff] |
Correct logic for obtaining the path to full recovery image Currently, an extra '/vendor' is appended in target_files_dir of make_recovery_patch.py, which will yield an erroneous path when attempting to build full recovery image on vendorimage-leas devices: SYSTEM/vendor/vendor/etc/recovery.img This patch addresses the issue by removing the extra '/vendor' of target_files_dir, and add checks for whether the target builds vendor image in MakeRecoveryPatch() as well. This ensures no recovery image will be generated with prebuilt vendor. Signed-off-by: Ricky Cheung <rcheung844@gmail.com> Change-Id: I2dc6e43537deb606dd01fb090add2595502055c1
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.