Small set of changes in gyp files to enable build for libchromeview for
MIPS-Android.
It also includes minor change in base/debug/stack_trace_android.cc to
redefine SIGSTKFLT for MIPS, since MIPS does not have SIGSTKFLT.
BUG=130022
TEST=build libchromeview
Review URL: https://chromiumcodereview.appspot.com/14241008
git-svn-id: http://src.chromium.org/svn/trunk/src/build@196938 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
gcc_version previously existed only under certain conditions; currently,
os_posix==1 and OS!="mac" and OS!="ios".
These same checks had to be repeated everywhere gcc_version was used, and
they often got out of sync (many places still do not check for OS!="ios",
for example).
We now always gcc_version. Its default value is 0, and it is then changed to
something meaningful under that condition mentioned above. This allows us to
remove the duplicated checks currently spread across the .gyp files in the
tree.
BUG=
Review URL: https://chromiumcodereview.appspot.com/13912027
git-svn-id: http://src.chromium.org/svn/trunk/src/build@196910 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This patch deprecates armv7 and adds arm_version that takes an integer
value representing the ARM architecture level.
In addition arm_arch, arm_tune, arm_fpu, arm_float_abi and arm_thumb can
be set to fine tune CPU related compiler flags, defaults are provided for
ARM versions 5 to 7.
BUG=234135
Review URL: https://chromiumcodereview.appspot.com/14065005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@196702 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The combination of generated shim headers, the system ICU targets being
type "none", and ui being a static library caused some dependencies to
be missed out when use_system_icu==1. Make ui a hard dependency to work
around this.
BUG=
Review URL: https://chromiumcodereview.appspot.com/14472005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@196700 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
In addition move C4355 to list of sanctioned compiler warning suppressions.
The warning was disabled globally for ~2 years, meaning the macro wasn't providing any value. Refer to bug and chromium-dev@ discussion for details.
BUG=234765
Review URL: https://chromiumcodereview.appspot.com/14472011
git-svn-id: http://src.chromium.org/svn/trunk/src/build@196671 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Speculating this is the cause of these OS X release builder hangs:
http://build.chromium.org/p/chromium.mac/builders/Mac%20Builder/builds/11074/steps/compile/logs/stdiohttp://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Mac/builds/12424/steps/compile/logs/stdio
Relevant compile output:
=== BUILD AGGREGATE TARGET base_unittests_run OF PROJECT base WITH CONFIGURATION Release ===
Check dependencies
PhaseScriptExecution "Rule \"isolate\"" ../xcodebuild/base.build/Release/base_unittests_run.build/Script-5816EF986C49795B2FAB6114.sh
cd /Volumes/data/b/build/slave/cr-mac-rel/build/src/base
/bin/sh -c /Volumes/data/b/build/slave/cr-mac-rel/build/src/base/../xcodebuild/base.build/Release/base_unittests_run.build/Script-5816EF986C49795B2FAB6114.sh
python ../tools/swarm_client/isolate.py check --outdir "/Volumes/data/b/build/slave/cr-mac-rel/build/src/base/../xcodebuild/Release/ " --variable PRODUCT_DIR "/Volumes/data/b/build/slave/cr-mac-rel/build/src/base/../xcodebuild/Release " --variable "OS=mac" --result "/Volumes/data/b/build/slave/cr-mac-rel/build/src/base/../xcodebuild/Release/base_unittests.isolated" --isolate "base_unittests.isolate" --ignore_broken_items
command timed out: 1200 seconds without output, attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=4205.819860
> Reenable test_isolate_mode=check by default on OSX.
>
> This is not necessary to default to noop anymore. Defaulting to check was
> disabled on OSX because a problem during archival with symlink path case. This
> was fixed inside swarm_client.
>
> R=csharp@chromium.org
> BUG=98637
>
> Review URL: https://chromiumcodereview.appspot.com/14404011TBR=maruel@chromium.org
Review URL: https://codereview.chromium.org/13996018
git-svn-id: http://src.chromium.org/svn/trunk/src/build@195664 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
asan's clang is currently pinned to a very old revision and hence includes
a very old plugin. Since all other bots run the plugin, we don't really
lose coverage by disabling the plugin on asan bots for now.
BUG=170629
TBR=glider
Review URL: https://chromiumcodereview.appspot.com/14305005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@195479 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Broke chromeos clang builder: Complains about libstdc++ 4.4, but is probably not
yet on precise.
Broke linux clang tests: unit_tests, content_unittests, components_unittests
all crash at startup with:
symbol lookup error: /b/build/slave/Linux_Clang__dbg_/build/src/out/Debug/lib/libcontent.so: undefined symbol: _ZN7content6Zygote26kMagicSandboxIPCDescriptorE
> clang: Build in C++11 mode on linux & cros too.
>
> But: Not yet on Android, not yet with asan, not yet with gcc.
> Only with clang, and only for linux & cros (in addition to mac,
> which has had this for a while).
>
> BUG=233330,233464
>
> Review URL: https://codereview.chromium.org/11468005TBR=thakis@chromium.org
Review URL: https://codereview.chromium.org/14328034
git-svn-id: http://src.chromium.org/svn/trunk/src/build@195091 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
There are a lot of warnings when build chromium with gcc4.8, which are
in "typedef ‘foo’ locally defined but not used" pattern. Add
"-Wno-unused-local-typedefs" to suppress these warnings.
BUG=227506
TEST=build with gcc4.8 and check no above warnings appear.
Review URL: https://chromiumcodereview.appspot.com/13811009
git-svn-id: http://src.chromium.org/svn/trunk/src/build@194779 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
With the component build, we tell Dalvik to load each library separately by name. Some of our library names conflict with android shared libraries resulting our library not getting loaded. When building for components on Android, change the suffix of libraries to "cr.so" e.g. libnetcr.so to avoid colliding with Android's copies
BUG=158821
Review URL: https://chromiumcodereview.appspot.com/13549002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@192258 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
For the component build, it is impractical/impossible to explicitly
list all library dependencies. This list is required (in dependency
order) for several of the apk-building steps.
For now, we will generate this list as follows:
Use readelf to find all transitive dependencies
Topologically sort those dependencies
Once we can expose this information from gyp
(http://crbug.com/2255588), it is straightforward to update this action
to use the gyp-exposed list of libraries.
BUG=158821
Review URL: https://chromiumcodereview.appspot.com/13261024
git-svn-id: http://src.chromium.org/svn/trunk/src/build@192103 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Add a gyp variable "android_managed_install" which defaults to off/0.
When this variable is 1, building an apk target will install that
target.
This will allow us to do crazy things with the install like pushing
native libraries independent from the apk they belong to.
This currently just does an "adb install -r <(apk_path)". I.e. it only
works for (the typical) single device attached workflow. This could
be made configurable to handle other cases (or maybe just install to all
devices attached, or just to the first device).
BUG=158821
Review URL: https://chromiumcodereview.appspot.com/13269002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@191840 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere.
BUG=159240,92909
Committed: r186925
Reverted: r186939 due to build errors
Committed: r187340
Committed: r187427
Reverted: r187668 due to a failing check in Canary, which was fixed here: r187681
Committed: r189518
Reverted: r189682, due to regression in Kraken (see crbug.com/222741)
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=191420
Reverted: r191441, due to new failing PDFResource unit test.
Review URL: https://chromiumcodereview.appspot.com/12378050
git-svn-id: http://src.chromium.org/svn/trunk/src/build@191510 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
> PPAPI: Remove threading options; it's always on
>
> This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere.
>
> BUG=159240,92909
>
>
> Committed: r186925
> Reverted: r186939 due to build errors
>
> Committed: r187340
>
> Committed: r187427
> Reverted: r187668 due to a failing check in Canary, which was fixed here: r187681
>
> Committed: r189518
> Reverted: r189682, due to regression in Kraken (see crbug.com/222741)
>
> Review URL: https://chromiumcodereview.appspot.com/12378050TBR=dmichael@chromium.org
Review URL: https://codereview.chromium.org/13328006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@191441 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This also re-enables thread checking for the host side resource and var trackers. Before, checking was disabled everywhere.
BUG=159240,92909
Committed: r186925
Reverted: r186939 due to build errors
Committed: r187340
Committed: r187427
Reverted: r187668 due to a failing check in Canary, which was fixed here: r187681
Committed: r189518
Reverted: r189682, due to regression in Kraken (see crbug.com/222741)
Review URL: https://chromiumcodereview.appspot.com/12378050
git-svn-id: http://src.chromium.org/svn/trunk/src/build@191420 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This enables Android layouts and Java code to use strings from
generated_resources.grd directly. Strings tagged with
formatter_data="android_java" in generated_resources.grd are used to produce an
Android strings xml file.
BUG=176069
Review URL: https://chromiumcodereview.appspot.com/12529025
git-svn-id: http://src.chromium.org/svn/trunk/src/build@190573 4ff67af0-8c30-449e-8e8b-ad334ec8d88c