| commit | 3367d1dc869aa287bede92b8ba29983fb423f338 | [log] [tgz] |
|---|---|---|
| author | Brint E. Kriebel <bekit@cyngn.com> | Wed Aug 13 12:27:38 2014 -0700 |
| committer | Jackeagle <jackeagle102@gmail.com> | Fri Aug 10 21:44:37 2018 -0400 |
| tree | 4597e83c4985b88224f2b9de106cf50d0645e9ae | |
| parent | add861e3019da2242f33c0744a5045e1540666cd [diff] |
build: Handle custom boot images properly When a pre-built image should be used, it should be stored in the target files zip so that it can be used with external signing processes. Original-Change-Id: I2661af9ac58af30bb9314b552775046d3abf44e0 Change-Id: I10b3bd0bb33489b8ffb26d16d002f8dd6ff405ad
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.