| commit | da8e0e7b92aea5fe061e0de102600bc5ae6fe91f | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Mon May 20 09:53:57 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon May 20 09:53:57 2019 -0700 |
| tree | a85c57ca9beb1c501830636957e7c999b7a24992 | |
| parent | 633ef2c32341b6f95dc193c1feee6ce11f92231e [diff] | |
| parent | aa3779a6166f0b273f772b0c50ddc19a475b8014 [diff] |
Add sign_apex.py that signs a given APEX file. am: f52dbb81fe am: aa3779a616 Change-Id: Ief6e9e21dc0212259239807b247a4da28e733ed0
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.