win: Add support for TargetMachine in VCLibrarianTool section

win: Add support for TargetMachine in VCLibrarianTool section

remoting_host_event_logger.lib was built from one .rc file and one .cc.
If unspecified, lib.exe appears to choose the architecture from the
first input file. As a compiled .res doesn't have an architecture, it
bailed and selected X64 (because the 2013 lib.exe is x64 host, I guess).
Resulting in:

FAILED: E:\b\depot_tools\python_bin\python.exe gyp-win-tool link-wrapper environment.x86 lib.exe /nologo /ignore:4221 /OUT:obj\remoting\remoting_host_event_logger.lib @obj\remoting\remoting_host_event_logger.lib.rsp
LINK : warning LNK4068: /MACHINE not specified; defaulting to X64

obj\remoting\host\remoting_host_event_logger.host_event_logger_win.obj : fatalerror LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

VCLibrarianTool supports TargetMachine the same as VCLinkerTool, but
we'd never used it before. Add support to the ninja/msvs generator,
and add a test for it.

R=thakis@chromium.org
BUG=309197
Committed: https://code.google.com/p/gyp/source/detail?r=1785

[Nico, 2013-11-12 06:21:55]

lgtm!

[scottmg, 2013-11-12 06:54:18]

Committed patchset #2 manually as r1785.