e74a38bc6d
Non-A/B devices need to include the DTBO image within the recovery partition to be self-sufficient and prevent OTA failures. Test: Ran 'm dist' and verified that the DTBO image was included in recovery.img using unpack_bootimg. Also ran 'make' and verified that the DTBO image was included in recovery.img using unpack_bootimg. Also tested that aosp_angler-userdebug could boot into recovery(including a fake dtbo.img in recovery image). Bug: 74763691 Change-Id: I38c9c395c95d21f4da42cfa646063bd4416f6bd8 |
||
|---|---|---|
| core | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.mk | ||
| Changes.md | ||
| CleanSpec.mk | ||
| OWNERS | ||
| README.md | ||
| Usage.txt | ||
| buildspec.mk.default | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| tapasHelp.sh | ||
README.md
Android Make Build System
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.