commit | fd39c26b3991c8fee14a6aa9bb295936096efeff | [log] [tgz] |
---|---|---|
author | Baligh Uddin <baligh@google.com> | Tue Aug 27 00:34:56 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Tue Aug 27 00:34:56 2019 -0700 |
tree | 124c85ede3891e4528d97d2daf593306cfa0b282 | |
parent | cc0234ba558486094d8bac26e189fd712eec43bd [diff] | |
parent | f518748b2b4f83dbc1b285d418f4ec800f5ddf58 [diff] |
DO NOT MERGE - Add a guard against deleting AVB_PUBKey. am: 39b8f9fc7d am: f518748b2b Change-Id: I349111540e765af64cdd0f915819e2a290c01ea1
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.