| commit | b2c4bb7e3ddcaa27242c1e4e78f69d7e39524cf9 | [log] [tgz] |
|---|---|---|
| author | Jeongik Cha <jeongik@google.com> | Mon Dec 17 14:45:15 2018 +0900 |
| committer | Jeongik Cha <jeongik@google.com> | Thu Jan 10 11:37:22 2019 +0900 |
| tree | 3806c64f1fb8168e38b893ce19bf665f88e1cd33 | |
| parent | 8d95a14476b5b1cb5a2af655ac5da4606c3b5c07 [diff] |
Dump and enforce certificate for apks Dump the list of APKs that aren't located at system partition and signed with system certificate. And when enforcement option is enabled, it makes build error if there is the apk that satisfies the condition above. Bug: 74699609 Test: m -j Test: m out/target/product/$(get_build_var TARGET_DEVICE)/certificate_violation_modules.txt Change-Id: I23c41f2665dd97abac3e77d1c82d81ff91b894eb
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.