Граф коммитов

10 Коммитов

Автор SHA1 Сообщение Дата
scheib 9fcf7fdf48 Comment that gyp_managed_install requires a userdebug flashed device.
Review URL: https://codereview.chromium.org/918833002

Cr-Original-Commit-Position: refs/heads/master@{#316014}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 036bf74db1cc3d68b9c1af2364f0a83674d7aee3
2015-02-12 19:13:45 +00:00
mlamouri 95f0ede9fd Always enable optimize_jni_generation on non-WebView builds.
It seems that the cons are fairly weak and the benefits might be worth it.
This flag breaks WebView builds.

BUG=None

Review URL: https://codereview.chromium.org/502743002

Cr-Original-Commit-Position: refs/heads/master@{#292458}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 23668752ea266ca59e788510fc9e4baaf0397895
2014-08-28 20:58:00 +00:00
aurimas@chromium.org 51e4184a01 Fix component build failure for users of developer_recommended_flags.gypi
BUG=None
NOTRY=true

Review URL: https://codereview.chromium.org/380913002

git-svn-id: http://src.chromium.org/svn/trunk/src/build@282149 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2014-07-09 22:38:26 +00:00
cjhopman@chromium.org ba517b8506 [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

Review URL: https://chromiumcodereview.appspot.com/14843017

git-svn-id: http://src.chromium.org/svn/trunk/src/build@208529 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-06-25 18:42:07 +00:00
dfalcantara@chromium.org 458e6b0e2b Revert "[Android] Support building standalone APK in component build"
This breaks the Android component build.

This reverts commit 125e64a9eb6406446fb864aea9fa887521f19616.
>> [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

BUG=
R=cjhopman@chromium.org

Review URL: https://codereview.chromium.org/17291013

git-svn-id: http://src.chromium.org/svn/trunk/src/build@207587 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-06-20 21:42:06 +00:00
cjhopman@chromium.org f00dfb88a8 [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

Review URL: https://chromiumcodereview.appspot.com/14843017

git-svn-id: http://src.chromium.org/svn/trunk/src/build@207516 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-06-20 19:51:29 +00:00
skyostil@google.com 283725629a 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: http://src.chromium.org/svn/trunk/src/build@207439 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-06-20 15:31:28 +00:00
cjhopman@chromium.org 7ad7e2169a [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: http://src.chromium.org/svn/trunk/src/build@207345 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-06-20 07:58:19 +00:00
cjhopman@chromium.org 56da9a9a88 [Android] Only set recommended flags if they are unset
This allows developers to force the values of individual flags in their
chrome/supplement.gypi. Add documentation for how a user can do that.

Also add a comment about the fastbuild option, but do not ever set it
by default.

NOTRY=true
BUG=158821

Review URL: https://chromiumcodereview.appspot.com/14366023

git-svn-id: http://src.chromium.org/svn/trunk/src/build@195334 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-04-19 23:27:06 +00:00
cjhopman@chromium.org 5da41d20c3 [Android] Add recommended.gypi with recommended settings
This gypi includes the recommended gyp settings for Chrome for Android
development, as well as instructions for using the settings.

NOTRY=true
BUG=158821

Review URL: https://codereview.chromium.org/14122013

git-svn-id: http://src.chromium.org/svn/trunk/src/build@194219 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2013-04-15 20:13:17 +00:00