Description[Android] Support building standalone APK in component build
Many people's workflows assume that they can install the APK created in
out/Debug/apks. With the component build that APK is actually an
"incomplete" APK that cannot be manually installed (or rather causes
obscure errors when manually installed).
This change does two things. First, it moves the "incomplete" APK
output to out/Debug/<package_name>/<ApkName>.apk. This should prevent
accidental installs of the "incomplete" APK. Second, it introduces an
option (create_standalone_apk) that when doing a component build, if
set, will merge the shared libraries into the "incomplete" APK to
create a standalone APK. This standalone APK will be created in
out/Debug/apks/.
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=207345
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=207516
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=208529
Patch Set 1 #
Total comments: 2
Patch Set 2 : Rebase #Patch Set 3 : Address nit #Patch Set 4 : Fix test apks #Patch Set 5 : #Patch Set 6 : Rebase #Patch Set 7 : #Patch Set 8 : Rebase #
Messages
Total messages: 15 (0 generated)
|