| commit | a6c5912e4da738a5d69fee11f82bb191e314e8ac | [log] [tgz] |
|---|---|---|
| author | Po Hu <po.hu@mediatek.com> | Wed Feb 16 08:41:29 2022 +0000 |
| committer | Daniel Norman <danielnorman@google.com> | Fri Feb 18 13:25:51 2022 -0800 |
| tree | 77e58460548bf2b36e1104b78d18c0a32cef058f | |
| parent | a84d13bc6e36fd2f103659eff67df9315af3d941 [diff] |
Fix ota_from_target_files error in non-AB VF For vendor freeze, vendor.img/odm.img is rebuilt and moved to the merged target files dir in a special build flow: https://android-review.googlesource.com/c/platform/build/+/1752968 But considering non-AB case, some more files are generated by MakeRecoveryPatch() along with vendor.img, such as: IMAGES/vendor.map VENDOR/etc/recovery.img VENDOR/bin/install-recovery.sh They should be copied to the merged target files dir as well, in order to pass the check in HasRecoveryPatch() and GetSparseImage(). Bug: 219871887 Test: Used to merge non-AB VF device Change-Id: I003186b30e700413d54ee1b7521bd03ba83ad3f5
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.