commit | e6d4fb5ae6425c7b12cd6342cd15ecd3005d2f82 | [log] [tgz] |
---|---|---|
author | Melisa Carranza Zuniga <melisacz@google.com> | Mon Mar 07 14:56:26 2022 +0100 |
committer | Melisa Carranza Zúñiga <melisacz@google.com> | Mon Mar 21 22:56:33 2022 +0000 |
tree | 049f64ff20be935b7af810e06c0882ab1fbd1d22 | |
parent | 0e3ed13950de029b58b72b80f0d4a9cb3c1c4293 [diff] |
Adding sepolicy sign params to sign_target_files_apks. Bug: b/217570541 Test: sign_target_files_apks --sepolicy_key=build/make/tools/releasetools/testdata/testkey_RSA4096.key --sepolicy_cert=build/make/tools/releasetools/testdata/testkey.x509.pem target_files.zip target_out.zip Change-Id: I4ae9f2a3297d10de68c6444dea1cd9996ad9dd11 Change-Id: I4a1ac7009ae0d6bb53c74bd34f8c74f12ea0a3b8
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.