| commit | c0f413f0ad567ef55417dd366e26e800553a472c | [log] [tgz] |
|---|---|---|
| author | Bill Peckham <bpeckham@google.com> | Thu Nov 07 11:27:02 2019 -0800 |
| committer | Bill Peckham <bpeckham@google.com> | Mon Dec 02 18:16:01 2019 +0000 |
| tree | a969bd6bb8bbbe59113cbe92ab33747ec9834e10 | |
| parent | 05c8db112a86218b8061a1dd2336567c6cee4be5 [diff] |
Don't generate recovery patch for A/B systems. An A/B system that has a recovery image should not generate the recovery patch. This change gates the creation of the recovery patch such that we create it only when the recovery image exists and only for non-A/B systems. Test: Build A/B system, verify that recovery patch is not present. Bug: 144104493 Change-Id: Ib570c21b73912c4e4b7a964b192abc15fde9a753
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.