| commit | ffbe6b97856968503c59515700884c6d60128717 | [log] [tgz] |
|---|---|---|
| author | Tianjie Xu <xunchang@google.com> | Fri Oct 19 14:34:15 2018 -0700 |
| committer | Tianjie Xu <xunchang@google.com> | Mon Oct 22 14:47:15 2018 -0700 |
| tree | 6ded58b000cb08fda962b90e80bfc19e27e86d79 | |
| parent | 0f693d3f25cf9323a9cf8ceb238d5a3c2e663f23 [diff] |
Install the ota keys under recovery as a zipfile Recovery can now parse the pem encoded x509 keys from a zipfile. So instead of dumping the keys into a text file with some intermediate format, we can simply create a zipfile with the keys. Bug: 116655889 Test: make bootimage and check the generated zipfile, run sign_target_files_apks Change-Id: Ib76feecfb26d6be713a07644e80ec96133759004
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.