commit | e0a977affd1a97764ac088e7de7386fa89f4b006 | [log] [tgz] |
---|---|---|
author | Melisa Carranza Zuniga <melisacz@google.com> | Thu Jun 16 18:44:27 2022 +0200 |
committer | Melisa Carranza Zuniga <melisacz@google.com> | Mon Jun 27 11:03:26 2022 +0200 |
tree | e806045c6f7e84c8346f693ad2a2e1e6fbd893c1 | |
parent | f68794510fcbfd10a38bdfbf8d5d6c1f6d206afb [diff] |
Add sign_sepolicy_path for a binary to sign sepolicy.apex. Bug: b/217570541 Test: sign_apex --container_key=testdata/testkey --payload_key=testdata/testkey_RSA4096.key --codename_to_api_level_map=S:31,T:32,UpsideDownCake:33 -e SEPolicy-33.zip=testdata/testkey com.android.sepolicy.apex signed_sepolicy.apex Change-Id: Ifdd1c6e7db07cbc4674450ab0e2226494c98605a
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.