commit | 3363a0b8d66e52f1e8eacd983f661ac385a72e1a | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Wed Feb 12 13:38:28 2020 -0800 |
committer | Steve Muckle <smuckle@google.com> | Wed Mar 04 10:54:56 2020 -0800 |
tree | 81bfdb79104ed0b927bab12dfb50bf6a28706258 | |
parent | 6bf4a7d0be45b720dae92249aab72c58247e3e72 [diff] |
initial GKI boot.img support The GKI boot.img should be generated alongside the GSI. To make this possible, define a flag (TARGET_NO_VENDOR_BOOT) that can be used to disable the generation of the vendor_boot image. Bug: 138323550 Change-Id: I91181853b26815e68a2fa2216b68579780d034dc
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.