| commit | 2237d06a7812b7d0b43ae2d39792baaf1913a911 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Mon Feb 11 10:15:22 2019 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Fri Feb 15 00:39:47 2019 +0900 |
| tree | fd1ab1e7aeb39d3de0409ebd5cf542f757c95710 | |
| parent | 87ec538ef1e5c3dc8d7a1171dfe664ecdfb0ecde [diff] |
Revert "Add APK container signing key/cert pairs for APEXes" This reverts commit 74f27716f30d2c5a4cad73868c6f173d44cc6257. The key/cert pairs for APEXes are moved to the same directory where the APEXes are defined. Test: Check this for all APEXes jarsigner -verify -verbose -certs out/target/product/blueline/system/apex/com.android.tzdata.apex shows ... X.509, CN=com.android.tzdata, OU=Android, O=Android, L=Mountain View, ST=California, C=US Change-Id: I8d867b434b93aa68cbc707fa20ed8dbd4cef755e
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.