win: Fix behaviour of MinimumRequiredVersion

Previous change for ninja set default subsystem to XP, but didn't do
anything for msvs. This broke the 2012 bot which is where the default
changed (I thought it was 2013 previously).

Now, use the MinimumRequiredVersion setting to determine this value,
which works in VS >= 2010 and emulate that in ninja.

Also, add another line to TestGyp.py so that gyptest.py works when
running on VS2013.

R=thakis@chromium.org
BUG=320371

Review URL: https://codereview.chromium.org/67373005

git-svn-id: http://gyp.googlecode.com/svn/trunk@1788 78cadc50-ecff-11dd-a971-7dbc132099af
xcode: Xcode 5 changes the "up_to_date_ending" again. This fix allows
most (but not all) tests to pass with Xcode 5.

BUG=gyp:381
R=thakis@chromium.org

Review URL: https://codereview.chromium.org/73063005

git-svn-id: http://gyp.googlecode.com/svn/trunk@1789 78cadc50-ecff-11dd-a971-7dbc132099af
ninja: When the installed Xcode is Xcode 5 or later, use ['x86_64'] as
the default value of ARCHS instead of ['i386']. This mimics the behavior
of the installed Xcode.

BUG=gyp:381
R=thakis@chromium.org

Review URL: https://codereview.chromium.org/74103002

git-svn-id: http://gyp.googlecode.com/svn/trunk@1790 78cadc50-ecff-11dd-a971-7dbc132099af
ninja: use cc and c++ instead of gcc and g++ by default on non-Windows.

See https://groups.google.com/forum/#!topic/gyp-developer/50IkuJBVGbU .

For Mac specifically:

g++ on my system is not Xcode's g++, but proper FSF GNU GCC g++. This
doesn't hurt Chromium, which sets clang as the compiler by default, but
does hurt projects that don't explicitly specify a compiler, including
the tests.

FSF GNU GCC g++ doesn't understand these options that xcode_emulation.py
adds:

g++: error: unrecognized command line option ‘-fasm-blocks’
g++: error: unrecognized command line option ‘-mpascal-strings’

R=thakis@chromium.org

Review URL: https://codereview.chromium.org/61293005

git-svn-id: http://gyp.googlecode.com/svn/trunk@1791 78cadc50-ecff-11dd-a971-7dbc132099af