e134399cab
This CL adds support that allows treating an APEX as pre-signed. We can skip signing an APEX with `-e <apex-name>=` and `--extra_apex_payload_key <apex-name>=`. Note that the payload_key and container_key must be in consistent state - either they're both PRESIGNED or none of them is. CheckApkAndApexKeysAvailable() has been updated to perform the sanity check. Bug: 123716522 Test: Run sign_target_files_apks.py with the above flags. Test: python -m unittest test_sign_target_files_apks Change-Id: Id1e2f3f2facd4a97a385983cc9b78c028f7e7e73 |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| buildspec.mk.default | ||
| Changes.md | ||
| CleanSpec.mk | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| OWNERS | ||
| README.md | ||
| tapasHelp.sh | ||
| Usage.txt | ||
Android Make Build System
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.