| commit | c59ebf9990d0f73443aef132c8cb6e496582ace8 | [log] [tgz] |
|---|---|---|
| author | Baligh Uddin <baligh@google.com> | Tue Jul 30 06:57:37 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Jul 30 06:57:37 2019 -0700 |
| tree | a90bd575a0dbd1e6e3e08e5f80433db4782507cb | |
| parent | 9008e80c8e817ffbd6bbdc7b195a0b04847badc8 [diff] | |
| parent | df238b4e41d29aa02988d6d8da8ed8e531a7a79f [diff] |
Select all .pem and .avbpubkey in otatools am: df238b4e41 Change-Id: I66d5e2e8d389d76134e8a629847c441019d049d5
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.