
In VS2013, remoting_host_event_logger.lib fails with: 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' This is because if unspecified, lib.exe chooses the target architecture based on the first input file. In this lib, the first file (there's only 2) happens to be a .res compiled from a .rc, which doesn't have an architecture. Because we use the amd64 toolchain, lib decides to guess that it should use x64. This fails to lib because the other .cc input is x86. After adding support for setting the architecture for libs in gyp here https://codereview.chromium.org/68133006/ this sets it explicitly on our libs too. R=cpu@chromium.org BUG=309197 Review URL: https://codereview.chromium.org/61893020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@234656 0039d316-1c4b-4281-b951-d872f2087c98
List of property sheets to be included by projects: common.vsprops Not used anymore. No-op. Kept for compatibility with current projects. debug.vsprops Enables debug settings. Must be included directly in Debug configuration. Includes internal\essential.vsprops. external_code.vsprops Contains settings made to simplify usage of external (non-Google) code. It relaxes the warning levels. Should be included after debug.vsprops or release.vsprops to override their settings. output_dll_copy.rules Run to enable automatic copy of DLL when they are as an input file in a vcproj project. release.vsprops Enables release settings. Must be included directly in Release configuration. Includes internal\essential.vsprops. Also includes "internal\release_impl$(CHROME_BUILD_TYPE).vsprops". So the behavior is dependant on the CHROME_BUILD_TYPE environment variable.