commit | 74f27716f30d2c5a4cad73868c6f173d44cc6257 | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Sat Jan 26 01:41:57 2019 +0900 |
committer | Jiyong Park <jiyong@google.com> | Sat Jan 26 02:19:58 2019 +0900 |
tree | 9e3f70583ceaee114a02a1f18dcfb09584c2e71f | |
parent | 1fdf5d789b95ea5bcfde5e5f00d6a4f6dcda57cf [diff] |
Add APK container signing key/cert pairs for APEXes Created via openssl req -x509 -newkey rsa:4096 -nodes -days 999999 -keyout key.pem -out com.android.tzdata.x509.pem openssl pkcs8 -topk8 -inform PEM -outform DER -in key.pem -out com.android.tzdata.pk8 -nocrypt Test: m com.android.tzdata 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: I19f6efaaa6468e65e9891e4e61704fb48f0b986a
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.