| commit | b3dda77f2a4ed4617feaeb56b144c4267d27ed47 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Wed Mar 11 16:03:07 2020 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Tue Mar 24 11:27:57 2020 -0700 |
| tree | 9d23f8a84f70375f823fc928c126038cb9dd5035 | |
| parent | 3363a0b8d66e52f1e8eacd983f661ac385a72e1a [diff] |
support multiple kernels, boot.img output In order to enable the delivery of multiple kernel variants with a platform build, add support for generating boot.img files from multiple kernels. The BOARD_KERNEL_BINARIES macro may be defined as a list of kernel binaries to be used (if not, the original behavior and assumption of a single kernel binary is preserved). Each kernel binary filename must begin with "kernel". Any extra text in the filename is appended to the boot.img name, so "kernel-gz" would generate "boot-gz.img". Bug: 151094943 Change-Id: Icbbf227e9561f4aa11ce10db8d7aa81c7a81eb5b
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.