| commit | a28c52661b29a41268cf7d0aefa7dbdc7719914e | [log] [tgz] |
|---|---|---|
| author | Tianjie <xunchang@google.com> | Mon Mar 23 18:14:09 2020 -0700 |
| committer | Tianjie Xu <xunchang@google.com> | Tue Mar 24 19:20:48 2020 +0000 |
| tree | 37e9601b87dcc45c14314afcc09b9c08b95da1c5 | |
| parent | c282ece0445fcfd30270c23ff66ef6db0c86d078 [diff] |
Build the payload image only during apk-in-apex signing When doing apk-in-apex signing, the package name is not reserved during the apex repacking. As a result, the name accidentally reverts to 'com.android.wifi' from 'com.google.android.wifi'. This cl changes the behavior to call 'apexer' by passing the '--payload_only' argument. So we don't build the apex file from scratch and the old AndroidManifest.xml will be reused. BUG: 152084536 Test: unit tests pass Change-Id: I8332b2ee84832fb196f2e1c4309abac5ab92e153 Merged-In: I8332b2ee84832fb196f2e1c4309abac5ab92e153
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.