commit | 7f093f70834432a5d202ae093cf3afd30b394730 | [log] [tgz] |
---|---|---|
author | Chris Gross <chrisgross@google.com> | Fri May 01 16:04:36 2020 -0700 |
committer | Chris Gross <chrisgross@google.com> | Mon May 04 08:26:29 2020 -0700 |
tree | 723827ba28ffa5f79b883cc9af674652baa01634 | |
parent | 4c69c2ff7256b97cbea3f9bd3298b1aafde12ec0 [diff] |
Allow bootjars in system_ext. Bug: 148385042 Test: Built and booted Pixel 3a both with and without a boot jar in system_ext. Change-Id: I17c95a6347552d4cf0db76c10d762c591b56d48a
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.