summaryrefslogtreecommitdiffstats
path: root/third_party
diff options
context:
space:
mode:
authorpeter@chromium.org <peter@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-16 19:27:42 +0000
committerpeter@chromium.org <peter@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-16 19:27:42 +0000
commit1c00dfc34ea2d6dfeab5d0d27933d3844ec123d2 (patch)
tree4b04bef3e46576dd53bb57b55ecfe3a54a270803 /third_party
parent08578162a10cf6c760a949ba826fe1f173168777 (diff)
downloadchromium_src-1c00dfc34ea2d6dfeab5d0d27933d3844ec123d2.zip
chromium_src-1c00dfc34ea2d6dfeab5d0d27933d3844ec123d2.tar.gz
chromium_src-1c00dfc34ea2d6dfeab5d0d27933d3844ec123d2.tar.bz2
Disable warnings in harfbuzz/ for Android when not using clang.
The Android NDK compilers, both on GCC 4.2 and on GCC 4.6, throw a warning about incompatible pointer signedness in one of harfbuzz' APIs. That's where the fun comes in: no flag is currently able to disable the warning when using Android's GCCs. We therefore have to disable all warnings. This is unfortunate, but we should still be getting sufficient coverage for other warnings from Linux and Android-clang builds. BUG= Review URL: https://chromiumcodereview.appspot.com/10829354 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151944 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party')
-rw-r--r--third_party/harfbuzz/harfbuzz.gyp12
1 files changed, 12 insertions, 0 deletions
diff --git a/third_party/harfbuzz/harfbuzz.gyp b/third_party/harfbuzz/harfbuzz.gyp
index bb7be86..76bd800 100644
--- a/third_party/harfbuzz/harfbuzz.gyp
+++ b/third_party/harfbuzz/harfbuzz.gyp
@@ -60,6 +60,18 @@
'../../build/linux/system.gyp:freetype2',
],
}],
+ ['OS == "android" and clang == 0', {
+ # The Android NDK compilers in the GCC 4.2 and 4.6 toolchains will
+ # show a warning about incompatible pointer signedness, but this
+ # warning cannot be disabled through an individual flag. To stop
+ # showing it, disable all warnings. Coverage is provided through
+ # clang builders, as well as Linux non-clang builders.
+ # TODO(beverloo): Re-enable warnings once the toolchains provide a
+ # way of disabling the specific warning.
+ 'cflags': [
+ '-w',
+ ],
+ }],
['clang == 1', {
'xcode_settings': {
'WARNING_CFLAGS': [