Reason for revert:
mini_installer somehow does not install icudtl.dat in the top product directory (alongside chrome.exe) leading to a failure in InitializeICU().
icudtl.dat is listed in both mini_installer.gypi and FILES.cfg for windows.
Original issue's description:
> Enable icu_use_data_file on Windows
>
>
> Set icu_use_data_file_flag to 1 on Windows in common.gypi and make the dependency on icudata conditional on 'icu_use_data_file_flag != 0' in common.gypi, base.gyp and net.gyp
>
> This also requires a change in third_party/icu/icu.gyp
> ( https://codereview.chromium.org/111723007/ ), which was rolled in by https://codereview.chromium.org/118313004/
>
> BUG=72633
> TEST=All windows builds work fine and there's no perf regression (start-up etc).
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=246387TBR=mark@chromium.org,scottmg@chromium.org,laforge@chromium.org,maruel@chromium.org,grt@chromium.org,wtc@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=72633
Review URL: https://codereview.chromium.org/139403006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@246632 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This will start covering the policy iOS build on the main waterfall. The code
in chrome/browser/policy is still disabled on that platform by default, but
the policy component and its unittests will be built.
This change also enables one policy on iOS, otherwise some parts of the build
break.
BUG=275292
Review URL: https://codereview.chromium.org/132233031
git-svn-id: http://src.chromium.org/svn/trunk/src/build@246422 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The C++ binary implements simple per-pixel algorithms for SpeedIndex
computation. This allows us to achieve near real-time processing without
bringing external dependencies.
The bitmaptools binary needs to be built before it can be used.
The overhead of spawning a child process for each frame is about 3ms.
BUG=323813
TEST=telemetry bitmap_unittest
Original review: https://codereview.chromium.org/136793022
TBR=tonyg,maruel
Review URL: https://codereview.chromium.org/131563009
git-svn-id: http://src.chromium.org/svn/trunk/src/build@246361 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
On Android/ARM we add -fomit-frame-pointer elsewhere in common.gypi.
Simply adding -fno-omit-frame-pointer when building with sanitizers is
not enough, because the former flag wins (it get added closer to the end
of the command line). Therefore, we also remove all -fomit-frame-pointer
flags under sanitizers.
BUG=325685
TEST=wait for the next clang roll, run asan tests on android
R=glider@chromium.org
Review URL: https://codereview.chromium.org/143873009
git-svn-id: http://src.chromium.org/svn/trunk/src/build@246256 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
We've switched to Aura on Linux (see chromium-dev threads). NPAPI plugins aren't supported on Linux Aura (also see chromium-dev thread). These tests should just be disabled.
> Revert of Reenable linux_aura on the main builders. (Again). (https://codereview.chromium.org/138033023/)
>
> Reason for revert:
> Blink layout tests are failing:
>
> http/tests/plugins/interrupted-get-url.html
> http/tests/plugins/third-party-cookie-accept-policy.html
> plugins/mouse-click-plugin-clears-selection.html
>
> Original issue's description:
> > Reenable linux_aura on the main builders. (Again).
> >
> > We upgraded the eu-strip binary so that it can deal with binaries that
> > are more than two gigabytes large. This should fix the crash on the
> > Google Chrome Linux builder, which was the only bot to break last night.
> >
> > BUG=319075,125106,303342,318961
> > NOTRY=True
> >
> > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245737
>
> TBR=erg@chromium.org
> NOTREECHECKS=true
> NOTRY=true
> BUG=319075,125106,303342,318961
>
> Review URL: https://codereview.chromium.org/143073002TBR=eustas@chromium.org
Review URL: https://codereview.chromium.org/137493007
git-svn-id: http://src.chromium.org/svn/trunk/src/build@246094 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Reason for revert:
Blink layout tests are failing:
http/tests/plugins/interrupted-get-url.html
http/tests/plugins/third-party-cookie-accept-policy.html
plugins/mouse-click-plugin-clears-selection.html
Original issue's description:
> Reenable linux_aura on the main builders. (Again).
>
> We upgraded the eu-strip binary so that it can deal with binaries that
> are more than two gigabytes large. This should fix the crash on the
> Google Chrome Linux builder, which was the only bot to break last night.
>
> BUG=319075,125106,303342,318961
> NOTRY=True
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245737TBR=erg@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=319075,125106,303342,318961
Review URL: https://codereview.chromium.org/143073002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@245865 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
For a short transition period, let envsetup.sh set the right GYP_DEFINES when
GOMA_DIR is set, so that people aren't broken immediately after this lands.
Also stop setting GOMA_COMPILER_PROXY_THREADS – if the value this sets
is truly better, that should be the default in goma, it shouldn't be set in
envsetup.sh (doing it in goma has the advantage that it works on all
platforms, also abstraction barriers, etc.)
BUG=332697
R=brettw@chromium.org, ilevy@chromium.org
Review URL: https://codereview.chromium.org/142393002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@245801 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This supports specifying the output_dir generator flag in the gn-generating-gyp
mode. The value of the output_dir flag is mapped to a gyp variable called gyp_output_dir
and a GN argument by the same name. References from gyp to gn-generated gyp files must
use this variable and references from BUILD.gn files must use the gn argument.
BUG=335760
TBR=brettw for build/config/BUILDCONFIG.gn (looked at in person)
Review URL: https://codereview.chromium.org/142223002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@245800 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
We upgraded the eu-strip binary so that it can deal with binaries that
are more than two gigabytes large. This should fix the crash on the
Google Chrome Linux builder, which was the only bot to break last night.
BUG=319075,125106,303342,318961
NOTRY=True
Review URL: https://codereview.chromium.org/138033023
git-svn-id: http://src.chromium.org/svn/trunk/src/build@245737 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Broke gpu_tests step on Android Debug GPU bot; see crbug.com/323813 for details.
> [telemetry] bitmaptools as a standalone executable
>
> The C++ binary implements simple per-pixel algorithms for SpeedIndex
> computation. This allows us to achieve near real-time processing without
> bringing external dependencies.
>
> The bitmaptools binary needs to be built before it can be used.
> The overhead of spawning a child process for each frame is about 3ms.
>
> BUG=323813
> TEST=telemetry bitmap_unittest
>
> Review URL: https://codereview.chromium.org/136793022TBR=szym@chromium.org
Review URL: https://codereview.chromium.org/138143020
git-svn-id: http://src.chromium.org/svn/trunk/src/build@245712 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
bauerb@chromium.org
eugenis@chromium.org
thakis@chromium.org
jshin@chromium.org
aedla@chromium.org
kochi@google.com
szym@chromium.org
zea@chromium.org
joaodasilva@chromium.org
caitkp@chromium.org
petarj@mips.com
uekawa@chromium.org
rsleevi@chromium.org
brettw@chromium.org
maruel@chromium.org
jam@chromium.org
eustas@chromium.org
jamesr@chromium.org
scottmg@chromium.org
erg@chromium.org
kbr@chromium.org
hinoka@google.com
pkasting@chromium.org