diff options
| author | skyostil@google.com <skyostil@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-20 15:31:28 +0000 |
|---|---|---|
| committer | skyostil@google.com <skyostil@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-20 15:31:28 +0000 |
| commit | 38ef36f44826408184e19a00fbba560a498d4677 (patch) | |
| tree | edf950576820f1a20342ed8c4eb36fad6030f006 /skia | |
| parent | a079f84dca0cf9c3fd6ae4f123491de917b9db6a (diff) | |
| download | chromium_src-38ef36f44826408184e19a00fbba560a498d4677.zip chromium_src-38ef36f44826408184e19a00fbba560a498d4677.tar.gz chromium_src-38ef36f44826408184e19a00fbba560a498d4677.tar.bz2 | |
Revert 207345 "[Android] Support building standalone APK in comp..."
This broke building of ChromeTest.apk. See:
http://chromegw.corp.google.com/i/clank.tot/builders/instrumentation-yakju-clankium-tot/builds/11555/steps/chrome_smoke_instrumentation_tests/logs/stdio
> [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
TBR=cjhopman@chromium.org
Review URL: https://codereview.chromium.org/17484010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207439 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'skia')
0 files changed, 0 insertions, 0 deletions