| commit | adf8096c77caacfd1478a91859deb5e798af1037 | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Mon Mar 18 14:20:52 2019 -0700 |
| committer | Daniel Norman <danielnorman@google.com> | Mon Mar 25 18:34:30 2019 +0000 |
| tree | df405e483daa4a73be704b38cca0801cace4e54d | |
| parent | 072795054a4284924067c5e7e9fa1ca56cb9598a [diff] |
Only call make_recovery_patch when BUILDING_SYSTEM_IMAGE. The recovery patch gets put in the SYSTEM directory. Placing the recovery patch here doesn't make sense when not building the system image, as is the case for merged (system + vendor) builds. Bug: 128838154 Test: Running make droid dist for a device target that sets PRODUCT_BUILD_SYSTEM_IMAGE to false. Change-Id: Ib5ce8c8490024199f82d0c093e9a7ae2de5f71f5
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.