| commit | a94189990693dd3662c03e02fae10175c4a1cd04 | [log] [tgz] |
|---|---|---|
| author | Hridya Valsaraju <hridya@google.com> | Mon Feb 04 10:35:25 2019 -0800 |
| committer | Hridya Valsaraju <hridya@google.com> | Tue Feb 05 18:19:39 2019 +0000 |
| tree | 6dd409533d66d386a9d2ecce2eed7e953278d78f | |
| parent | 20258b55b6b24a4968ef78587a563848108703f9 [diff] |
Allow for a separate recovery DTBO to be used for non-A/B devices. This CL allows for a separate recovery DTBO to be used by specifying it with the board config variable BOARD_PREBUILT_RECOVERY_DTBOIMAGE. Bug: 123889996 Test: make recoveryimage and make dist on a target that builds recovery.img and unpack_bootimg.py to test that BOARD_PREBUILT_RECOVERY_DTBOIMAGE gets used as the recovery DTBO. Change-Id: I6f83f37c3c894b2acddab1000224cd433649faa1
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.