Disable /analyze for the libexif and yasm projects to hack around internal compiler errors

third_party/libexif/libexif.gyp

Index: third_party/libexif/libexif.gyp
diff --git a/third_party/libexif/libexif.gyp b/third_party/libexif/libexif.gyp
index efb17026927947de9e8a4174b0e92ff15c8c5bce..9f16450e6627a0439ce86a0f0de1e15b51b3fde2 100644
--- a/third_party/libexif/libexif.gyp
+++ b/third_party/libexif/libexif.gyp
@@ -91,6 +91,16 @@
                 4018, # size/unsigned mismatch
                 4267, # size_t -> ExifLong truncation on amd64
               ],
+              # As of VS 2013 Update 3, building this project with /analyze hits an

[Lei Zhang, 2014/10/29 22:33:42]

Would you mind limiting comments to 80 chars/line? Long urls and actual gyp code
are exempt.

+              # internal compiler error on exif-entry.c. This halts the build and
+              # prevents subsequent analysis. Therefore, /analyze is disabled for
+              # this project. See this bug for details:
+              # https://connect.microsoft.com/VisualStudio/feedback/details/1014689/internal-compiler-error
+              'msvs_settings': {
+                'VCCLCompilerTool': {
+                  'AdditionalOptions!': [ '/analyze' ]
+                },
+              },
             }],
           ],
         },