| commit | 1143aaf7729f7489808be7a288905d15a738706e | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Fri Jan 13 09:45:00 2023 -0800 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Tue Jan 17 17:11:55 2023 +0000 |
| tree | 59fc0dc5cc0182f8662998a83a12868bac719b15 | |
| parent | 12d8a595136db47c4808a0de4731b207778f78aa [diff] |
Fix generic ramdisk build failures on dedicated recovery partitions For targets with BoardUsesRecoveryAsBoot set to true, binaries in generic_ramdisk are installed to $OUT/recovery/root/first_stage_ramdisk This path is not on generic_ramdisk.mk 's allowlist, hence build fails. To fix the failure, add $OUT/recovery/root/first_stage_ramdisk/system to allow list. Test: th, lunch eos-userdebug(a dedicated recovery partition target) and build. Bug: 265477065 Change-Id: I89cf229adc028a7e5de632b9a3188ecb411de735
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.