| commit | 95445e6913568e27e3b64d90494d20d5c829121d | [log] [tgz] |
|---|---|---|
| author | Jaewoong Jung <jungjw@google.com> | Thu Apr 02 13:01:08 2020 -0700 |
| committer | Jaewoong Jung <jungjw@google.com> | Mon Apr 06 13:42:23 2020 -0700 |
| tree | dddb2f93c34d9a96b28d4b182e440dfd8b17b1bc | |
| parent | 0889aaeeae27a59ee8ddfea4f2baa67179fd23bb [diff] |
Add signing certificate lineage file support. Also add multi-cert support to prebuilt apps so that they can benefit from the new lineage feature. (This is a cherry-pick change.) Test: m GoogleServicesFramework w/ modified build rules Test: m PrebuiltGmsCore w/ modified build rules Test: apksigner lineage -v --print-certs -in <built_module_path> Fixes: 152897457 Change-Id: If7d5d4bd308629c8340231520214c76c8a568a65 Merged-In: If7d5d4bd308629c8340231520214c76c8a568a65
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.