1 # By default gyp/msbuild build for 32-bit Windows. This gyp include file
2 # defines configurations for both 32-bit and 64-bit Windows. To use it, run:
4 # C:\...\winpty\src>gyp -I configurations.gypi
6 # This command generates Visual Studio project files with a Release
7 # configuration and two Platforms--Win32 and x64. Both can be built:
9 # C:\...\winpty\src>msbuild winpty.sln /p:Platform=Win32
10 # C:\...\winpty\src>msbuild winpty.sln /p:Platform=x64
12 # The output is placed in:
14 # C:\...\winpty\src\Release\Win32
15 # C:\...\winpty\src\Release\x64
17 # Windows XP note: By default, the project files will use the default "toolset"
18 # for the given MSVC version. For MSVC 2013 and MSVC 2015, the default toolset
19 # generates binaries that do not run on Windows XP. To target Windows XP,
20 # select the XP-specific toolset by passing
21 # -D WINPTY_MSBUILD_TOOLSET={v120_xp,v140_xp} to gyp (v120_xp == MSVC 2013,
22 # v140_xp == MSVC 2015). Unfortunately, it isn't possible to have a single
23 # project file with configurations for both XP and post-XP. This seems to be a
24 # limitation of the MSVC project file format.
26 # This file is not included by default, because I suspect it would interfere
27 # with node-gyp, which has a different system for building 32-vs-64-bit
28 # binaries. It uses a common.gypi, and the project files it generates can only
29 # build a single architecture, the output paths are not differentiated by
34 'WINPTY_MSBUILD_TOOLSET%': '',
37 'default_configuration': 'Release_Win32',
40 'msvs_configuration_platform': 'Win32',
43 'msvs_configuration_platform': 'x64',
46 'msvs_configuration_attributes': {
47 'OutputDirectory': '$(SolutionDir)$(ConfigurationName)\\$(Platform)',
48 'IntermediateDirectory': '$(ConfigurationName)\\$(Platform)\\obj\\$(ProjectName)',
52 'SubSystem': '1', # /SUBSYSTEM:CONSOLE
55 'RuntimeLibrary': '0', # MultiThreaded (/MT)
58 'msbuild_toolset' : '<(WINPTY_MSBUILD_TOOLSET)',