Support MASM in MSBuild and Winja

Support MASM in MSBuild and Winja

BUG=none

[Ryan Sleevi, 2013-01-03 00:33:42]

Scott: How do you feel about this approach?

This handles the VS2010+ when using the MSVS generator, and all versions with
Ninja (presuming that, if using VS2008 != SP1, that ml64/the WDK is on the
path).

One thing that I'm not sure of, when looking at things, is that the Ninja
generator treats RC include dirs differently than the MSBuild generator. I have
maintained that pattern with respect to MASM include dirs, but I suspect that
instead, Winja should be fixed. Compare _GetIncludeDirs() of msvs.py with
ninja.py's WriteSources to see this difference.

[Ryan Sleevi, 2013-01-03 00:34:02]

Oh, and tests forthcoming, provided the design is acceptable.

[scottmg, 2013-01-03 03:36:39]

Looks fine to me with tests, but adding bradn as I'm not that familiar with the
msvs generator.

You're right about the include dirs. I guess Chromium doesn't need that
functionality (?) so we didn't notice on the winja build. Of these
http://code.google.com/searchframe#search/&exact_package=chromium&q=resource_...
I know at least content_shell works, so it's possible the different set of
include dirs isn't actually necessary any longer.

https://codereview.chromium.org/11742015/diff/1/pylib/gyp/generator/msvs.py
File pylib/gyp/generator/msvs.py (right):

https://codereview.chromium.org/11742015/diff/1/pylib/gyp/generator/msvs.py#n...
pylib/gyp/generator/msvs.py:1098: directory paths, MASM inclue directory paths)
inclue

[Ryan Sleevi, 2013-01-07 02:10:17]

scott, brad: Please take a look at patchset 2, which has been updated with
tests.

(Apologies for the inter-diff spew. Completed the tests on another system with a
GYP checkout at a different version)

[scottmg, 2013-01-07 16:17:20]

lgtm