diff options
| author | cjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-20 07:58:19 +0000 |
|---|---|---|
| committer | cjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-20 07:58:19 +0000 |
| commit | 7aea76b94b0fc1d7f0c65aa8da195852157d1bd7 (patch) | |
| tree | 760117ea8d83c975cc32841b516f7015c99b3595 /sync | |
| parent | 30c98bbd310b123082954cc88955725c265517a6 (diff) | |
| download | chromium_src-7aea76b94b0fc1d7f0c65aa8da195852157d1bd7.zip chromium_src-7aea76b94b0fc1d7f0c65aa8da195852157d1bd7.tar.gz chromium_src-7aea76b94b0fc1d7f0c65aa8da195852157d1bd7.tar.bz2 | |
[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/.
Review URL: https://chromiumcodereview.appspot.com/14843017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207345 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync')
0 files changed, 0 insertions, 0 deletions