|author||Tao Bao <email@example.com>||Thu May 09 16:54:15 2019 -0700|
|committer||Tao Bao <firstname.lastname@example.org>||Mon May 13 12:41:26 2019 -0700|
Add sign_apex.py that signs a given APEX file. This CL moves SignApex() from sign_target_files_apks into apex_utils, and adds sign_apex that allows signing a standalone APEX file directly. Test: Run the following command and check the output file. $ build/make/tools/releasetools/sign_apex.py \ -v \ --container_key \ build/make/target/product/security/testkey.x509.pem \ --payload_key external/avb/test/data/testkey_rsa4096.pem \ --payload_extra_args \ "--signing_helper_with_files ./signing-helper.sh" \ foo.apex \ signed-foo.apex Test: Run sign_target_files_apks.py on crosshatch target_files.zip. Change-Id: I4b2422fd5cb1c60a3aa94511475e2a0e5b1666ca
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.