commit | 759d0c8cb2e440a7b3f8929518ee55281b3f58dd | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Mon Mar 16 19:13:46 2020 -0700 |
committer | Steve Muckle <smuckle@google.com> | Tue Apr 14 15:40:01 2020 -0700 |
tree | 52e9f92ea28694ef689ebfe81ea121118ba79048 | |
parent | e51409b68e0230bdd998b2905345836c5709687e [diff] |
Enable non-v3 recovery image with v3 boot image Add support for building a non-v3 recovery image along with a v3 boot.img and vendor_boot image. Bug: 150825361 Change-Id: I80d4e71ff09b83dd1c7f9accb4de99a30f95f4bf Merged-In: I80d4e71ff09b83dd1c7f9accb4de99a30f95f4bf
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.