This modifies the gclient hook to remove files that were inadvertently downloaded by a previous version of the script.
BUG=414826
Review URL: https://codereview.chromium.org/586063002
Cr-Original-Commit-Position: refs/heads/master@{#295763}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: f3b3b3bbeb8ed28ffa0c7580650a1d2ef29dade2
libc++ is the recommended C++ library for iOS development so use
it by default when targeting iOS.
clang ToT ships with all the required header and libraries to
support compiling with -stdlib=libc++ so remove the exception.
BUG=366744
Review URL: https://codereview.chromium.org/589513003
Cr-Original-Commit-Position: refs/heads/master@{#295715}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 7da3d8874ba759574edf778c58de024fe0974925
The target_arch should be ia32 for x86 builders. This is causing the x86 try and
fyi bots to fail during runhooks because it doesnt match a case in common.gypi.
BUG=359644
TBR=cmp@chromium.org
Review URL: https://codereview.chromium.org/581173004
Cr-Original-Commit-Position: refs/heads/master@{#295644}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 99fa5464cb1b1ba9af0dee4438f182de5c0847ea
java_cpp_enum.gypi was creating all enums in the same root folder and
then adding that folder to its dependents generated_src_dirs. This has
two issues: first, incremental builds will include stale files when
things are moved/renamed/etc. second, all libraries that depend on such
an enum target will actually compile and include all the enum targets
(and in fact may even include different versions of one enum in
different libraries).
This change just makes each such target use its own unique directory
(this will still have the stale enum issue when renaming an enum if the
target name doesn't change, but that is very rare).
The GN version already used unique directories.
TBR=mkosiba
Review URL: https://codereview.chromium.org/578363002
Cr-Original-Commit-Position: refs/heads/master@{#295595}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: e98bcec0ee81f43526ad06a2e27a1cdc3ef7f190
This might have been useful before while trying to get the system running. But now we have swarming running on Linux/Mac/Windows trybots, so it's not so useful. It's also confusing when tests fail on swarming machines because an isolate file referred to a binary that wasn't in the dependencies.
BUG=414808
Review URL: https://codereview.chromium.org/575363002
Cr-Original-Commit-Position: refs/heads/master@{#295514}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 6d2b3cd041bcded84f6f82f1fbac2348e2d7a9df
This patch also removes a call to AdbInterface.StartInstrumentation and
implements some of the functionality of am_instrument_parser.py.
BUG=408585
Review URL: https://codereview.chromium.org/558883003
Cr-Original-Commit-Position: refs/heads/master@{#295491}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: cbcc115def0fe5d2cf4c2018fccbbc16fd4c5aba
Fastbuild does not imply "faster build". Setting it to 1 or 2
on Android implies no debug information is generated and
nothing more.
BUG=411909
Review URL: https://codereview.chromium.org/583593004
Cr-Original-Commit-Position: refs/heads/master@{#295475}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 45e80089827142cec7f37d71704f7d6d4d579689
This has several changes:
apks no longer export information about resources (this means to get
resources, a target must depend on the android_resources target).
libraries are only built against their direct resource dependencies. If
a library refers directly to some resource id, it should depend directly
on the corresponding android_resources target.
When building an apk, we now properly create the R.java files for all
the packages of all the apk's resource dependencies.
Since an apk will always have a resources srcjar, it will always have
java code (so remove the no-java path).
BUG=359249
Review URL: https://codereview.chromium.org/570033002
Cr-Original-Commit-Position: refs/heads/master@{#295362}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: fed93a9b98c45ad7b0c8d3e3b0b9805d5a5107ac
This updates Chromium's clang version to r216630 with
r216684 cherry-picked to fix an ASan issue.
It also changes the build script for Clang to use CMake
instead of Autoconf. The ASan team say this configuration
is better tested, and it also makes us consistent with
the Windows Clang build which already uses CMake.
BUG=400849
R=thakis@chromium.org
TBR=brettw
Review URL: https://codereview.chromium.org/575833003
Cr-Original-Commit-Position: refs/heads/master@{#295289}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: bb493574c5f5ca5b572849676b69ab7bfec9828d
This gets the //chrome subtree down to a fairly small number of build
errors on Android. Most of the changes are making features not enabled
on android like extensions and plugins properly guarded. This also adds
a few jni targets and fixes up some bitrotted bits.
R=brettw@chromium.org, cjhopman@chromium.org
Review URL: https://codereview.chromium.org/571863002
Cr-Original-Commit-Position: refs/heads/master@{#295231}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 2ed4d695d6cf2917fc0e52f767d629fbefa7a1f9
- Use bundled binutils by adding to cflags -B
- Enables dwarf-fission based on bundling (maybe correct?)
- Makes differ normalize -B paths so they can be compared between gyp/gn.
R=brettw@chromium.org
BUG=335824
Review URL: https://codereview.chromium.org/568613002
Cr-Original-Commit-Position: refs/heads/master@{#295185}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 416440522fa2e5034c76a2adbe069bc7c6faaf55
This updates Chromium's clang version to r216630 with
r216684 cherry-picked to fix an ASan issue.
It also changes the build script for Clang to use CMake
instead of Autoconf. The ASan team say this configuration
is better tested, and it also makes us consistent with
the Windows Clang build which already uses CMake.
BUG=400849
R=thakis@chromium.org
TBR=brettw
Review URL: https://codereview.chromium.org/578623002
Cr-Original-Commit-Position: refs/heads/master@{#295099}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 3853ffa861dc43537f23c21a3fc4104c6f08c3a2
While installing on non-ubuntu systems, the shell script,
build/install-build-deps.sh has an option '--unsupported' to override
the system checks. The same is not applied while installing the android
deps. The parameters to install-build-deps-android.sh should be passed
on to install-build-deps.sh.
R=thakis@chromium.org
NOTRY=true
Review URL: https://codereview.chromium.org/578503002
Cr-Original-Commit-Position: refs/heads/master@{#295088}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 7e300f8e14c22e315eb1af28e9fe57c4ebcb13ef
Partial revert of android_webview: stop using system ICU. (patchset #1 id:1 of https://codereview.chromium.org/541753002/)
Reason for revert:
We can't accept this size increase at present; revert until we've worked out what to do about it.
Original issue's description:
> android_webview: stop using system ICU.
>
> To support unbundled updates we need to stop depending on system
> libraries. Disable using the system version of ICU and instead link
> Chromium's copy.
>
> This increases binary size by ~7MB.
>
> BUG=409851
>
> Committed: https://crrev.com/48e43572c0bfef2b1434d7f330da86cc7770b592
> Cr-Commit-Position: refs/heads/master@{#293510}
BUG=409851
Review URL: https://codereview.chromium.org/570383002
Cr-Original-Commit-Position: refs/heads/master@{#295083}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 96256bfea5c496aa70b1913555b1e1c7f166c426
The multiple_proguards_test_apk target used guava as an example for
something that needed to be proguarded out to ensure no proguard
warnings.
Since guava is going away, this CL moves the bad code into chromium
directly so there is no need for guava.
It does bad things which produce warnings, so they are silenced by
telling GYP that it is not chromium code.
BUG=412673
Review URL: https://codereview.chromium.org/571203003
Cr-Original-Commit-Position: refs/heads/master@{#294950}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 1c8fb8003d7d8e338c0bd277d3ab6bdff97e75df
Also update the name of the asan dynamic runtime thunk .lib since it was changed in LLVM r217673.
After this change, component ASan build should be able to report NULL derefs and other AVs the same way as the static build does.
BUG=345874
Review URL: https://codereview.chromium.org/573743002
Cr-Original-Commit-Position: refs/heads/master@{#294857}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 1d8adb2349f07f2595319f4ef7389001d3e9fd8f
PushDataDeps takes a long time even when all files are on the device
because calculating the digests of all the files takes _much_ longer
on a device than it does on a host.
Skipping the push step during test listing -- where the data deps are
unnecessary -- means that we don't try to push files twice in each
gtest run, so we skip all of the device-side MD5 calculations that
would happen in the second run.
BUG=400440
Review URL: https://codereview.chromium.org/560133002
Cr-Original-Commit-Position: refs/heads/master@{#294667}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 5c10479a0c3572cd41062b453c3e85527b5cfbad
This is a reland of dd7edfa67 which was reverted in 80a9a88f4c for build
failures. It also includes a BoringSSL roll and build changes to avoid adding a
static initializer.
This is a much much larger change than the diff suggests. If it breaks
something, please revert first and ask questions later.
BUG=338885
TBR=brettw
Review URL: https://codereview.chromium.org/568643003
Cr-Original-Commit-Position: refs/heads/master@{#294589}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 71c13e6ac01d5cdc49ca40e8e9301d5142d85018
This CL adds support for the mojo_base target on iOS that will be required to
implement the Mojo support that is feasible on iOS (namely, C++-C++
communication via Mojo and mojom interfaces).
Review URL: https://codereview.chromium.org/528763002
Cr-Original-Commit-Position: refs/heads/master@{#294580}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 475263c6949bad244ed906d92b349a32843c351e
- Don't remove -fno-ident from gyp build (was added about 3y ago, seemingly unnecessary for current clang)
- Add -fno-slp-vectorize to GN to make builds match (both to be removed after next clang roll)
- Make usage of -Wno-reserved-user-defined-literal match (required for dbus pre-trusty)
- Add -march=x86-64 to gn cflags
- Default symbol_level based on is_debug, and turn it off by default in Release (same as gyp)
Also, fiddle with output of gyp_flag_compare.py.
R=brettw@chromium.org
BUG=335824
Review URL: https://codereview.chromium.org/562383002
Cr-Original-Commit-Position: refs/heads/master@{#294489}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 29682b848742042388ebd29c9df775f074c1414c
Create a standalone executable that plumbs public Mojo API calls into a NaCl
sandbox. This allows the public Mojo unit tests to run inside NaCl.
BUG=401761
Review URL: https://codereview.chromium.org/385983008
Cr-Original-Commit-Position: refs/heads/master@{#294484}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 95d2d4025c767fbc5669377aae457a4bfb5ca46b
John Abd-El-Malek
chrisha
kulkarni.a
jmadill
sdefresne
Henrik Kjellander
navabi
hans
cjhopman
jbudorick
fdegans
Balazs Engedy
eugenis
feng
Dirk Pranke
Aurimas Liutikas
Robert Iannucci
ckocagil
primiano
James Robinson
gunsch
aurimas
scottmg
resetswitch
vivek.vg
torne
msarda
bradnelson
nyquist
timurrrr
davidben
blundell
ncbray