Turn on warnings as errors for (most) third_party code on Windows

Can't quite be fully enabled yet due to not-yet-fixed third party
dependencies. Without it enabled, other packages regress while we're fixing
things. So, add a flag for now so warnings-freeness can be ratcheted forward
by having it on for most packages, but off for a few.

Also, disable warning in qcms (fixed upstream by a large refactoring, not
worth rolling for), and disable two minor warnings in yasm (patch posted
upstream for a few months, but maintainer does not seem motivated to merge).

Fix release-only warning in leveldatabase/env_chromium.cc. Was calling exit(1)
in a leaky destructor.

Fix a warning in lzma_sdk (missing an include).

Disable a silly warning in Release builds of skia and memory_watcher (that
/GS is not working because optimization is disabled).

Warning are currently tolerated in libvpx and mesa.

Cannot be committed until http://chromiumcodereview.appspot.com/10823426/ has
landed.

R=thakis@chromium.org
BUG=126483,140121, 143877
TEST=


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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153092 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 1 insertions, 1 deletions

diff --git a/DEPS b/DEPS
index 8d63081..2b38fb2 100644
--- a/DEPS
+++ b/DEPS
@@ -20,7 +20,7 @@ vars = {
 
   "libjingle_revision": "170",
   "libphonenumber_revision": "456",
-  "libvpx_revision": "150392",
+  "libvpx_revision": "152423",
   "lss_revision": "11",
 
   # These two FFmpeg variables must be updated together.  One is used for SVN