commit | 39b8f9fc7dc54639e94e3fc146f8efa5ca5eb758 | [log] [tgz] |
---|---|---|
author | Baligh Uddin <baligh@google.com> | Sun Aug 25 12:01:44 2019 -0700 |
committer | Baligh Uddin <baligh@google.com> | Sun Aug 25 22:20:36 2019 -0700 |
tree | 271b3aaf52449621c85c6436d0f60d2968af8aa7 | |
parent | e840881168bd5a029657537be36a1160b182df91 [diff] |
DO NOT MERGE - Add a guard against deleting AVB_PUBKey. The avb_pubkey may not be present, if the apex was initially unsigned or generated from a bundle. In this case, running sign_apex to generate a signed apex binary would result in an error. This fix checks for presense of avbpubkey before attempting the deletion BUG: 139994107 Change-Id: I3cb2e88a11ad8797e38ba5fb98c96a4ec4135fc8
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.