moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-25 17:48:48 -05:00
Code Issues Releases Wiki Activity
a4554b2c5e
curl/projects/Windows/VC11/lib/libcurl.tmpl

2401 lines
148 KiB
Cheetah
Raw Normal View History

build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup Label="ProjectConfigurations">
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ProjectConfiguration Include="DLL Debug - DLL wolfSSL|Win32">
<Configuration>DLL Debug - DLL wolfSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug - DLL wolfSSL|x64">
<Configuration>DLL Debug - DLL wolfSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32">
<Configuration>DLL Debug - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug - DLL OpenSSL - DLL LibSSH2|x64">
<Configuration>DLL Debug - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug - DLL OpenSSL|Win32">
<Configuration>DLL Debug - DLL OpenSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug - DLL OpenSSL|x64">
<Configuration>DLL Debug - DLL OpenSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ProjectConfiguration Include="DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32">
<Configuration>DLL Debug - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug - DLL Windows SSPI - DLL WinIDN|x64">
<Configuration>DLL Debug - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="DLL Debug - DLL Windows SSPI|Win32">
<Configuration>DLL Debug - DLL Windows SSPI</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug - DLL Windows SSPI|x64">
<Configuration>DLL Debug - DLL Windows SSPI</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug|Win32">
<Configuration>DLL Debug</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Debug|x64">
<Configuration>DLL Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ProjectConfiguration Include="DLL Release - DLL wolfSSL|Win32">
<Configuration>DLL Release - DLL wolfSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release - DLL wolfSSL|x64">
<Configuration>DLL Release - DLL wolfSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="DLL Release - DLL OpenSSL - DLL LibSSH2|Win32">
<Configuration>DLL Release - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release - DLL OpenSSL - DLL LibSSH2|x64">
<Configuration>DLL Release - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release - DLL OpenSSL|Win32">
<Configuration>DLL Release - DLL OpenSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release - DLL OpenSSL|x64">
<Configuration>DLL Release - DLL OpenSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ProjectConfiguration Include="DLL Release - DLL Windows SSPI - DLL WinIDN|Win32">
<Configuration>DLL Release - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release - DLL Windows SSPI - DLL WinIDN|x64">
<Configuration>DLL Release - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="DLL Release - DLL Windows SSPI|Win32">
<Configuration>DLL Release - DLL Windows SSPI</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release - DLL Windows SSPI|x64">
<Configuration>DLL Release - DLL Windows SSPI</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release|Win32">
<Configuration>DLL Release</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="DLL Release|x64">
<Configuration>DLL Release</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32">
<Configuration>LIB Debug - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - DLL OpenSSL - DLL LibSSH2|x64">
<Configuration>LIB Debug - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - DLL OpenSSL|Win32">
<Configuration>LIB Debug - DLL OpenSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - DLL OpenSSL|x64">
<Configuration>LIB Debug - DLL OpenSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ProjectConfiguration Include="LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32">
<Configuration>LIB Debug - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - DLL Windows SSPI - DLL WinIDN|x64">
<Configuration>LIB Debug - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="LIB Debug - DLL Windows SSPI|Win32">
<Configuration>LIB Debug - DLL Windows SSPI</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - DLL Windows SSPI|x64">
<Configuration>LIB Debug - DLL Windows SSPI</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ProjectConfiguration Include="LIB Debug - LIB wolfSSL|Win32">
<Configuration>LIB Debug - LIB wolfSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - LIB wolfSSL|x64">
<Configuration>LIB Debug - LIB wolfSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32">
<Configuration>LIB Debug - LIB OpenSSL - LIB LibSSH2</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - LIB OpenSSL - LIB LibSSH2|x64">
<Configuration>LIB Debug - LIB OpenSSL - LIB LibSSH2</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - LIB OpenSSL|Win32">
<Configuration>LIB Debug - LIB OpenSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug - LIB OpenSSL|x64">
<Configuration>LIB Debug - LIB OpenSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug|Win32">
<Configuration>LIB Debug</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Debug|x64">
<Configuration>LIB Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - DLL OpenSSL - DLL LibSSH2|Win32">
<Configuration>LIB Release - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - DLL OpenSSL - DLL LibSSH2|x64">
<Configuration>LIB Release - DLL OpenSSL - DLL LibSSH2</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - DLL OpenSSL|Win32">
<Configuration>LIB Release - DLL OpenSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - DLL OpenSSL|x64">
<Configuration>LIB Release - DLL OpenSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ProjectConfiguration Include="LIB Release - DLL Windows SSPI - DLL WinIDN|Win32">
<Configuration>LIB Release - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - DLL Windows SSPI - DLL WinIDN|x64">
<Configuration>LIB Release - DLL Windows SSPI - DLL WinIDN</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="LIB Release - DLL Windows SSPI|Win32">
<Configuration>LIB Release - DLL Windows SSPI</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - DLL Windows SSPI|x64">
<Configuration>LIB Release - DLL Windows SSPI</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ProjectConfiguration Include="LIB Release - LIB wolfSSL|Win32">
<Configuration>LIB Release - LIB wolfSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - LIB wolfSSL|x64">
<Configuration>LIB Release - LIB wolfSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ProjectConfiguration Include="LIB Release - LIB OpenSSL - LIB LibSSH2|Win32">
<Configuration>LIB Release - LIB OpenSSL - LIB LibSSH2</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - LIB OpenSSL - LIB LibSSH2|x64">
<Configuration>LIB Release - LIB OpenSSL - LIB LibSSH2</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - LIB OpenSSL|Win32">
<Configuration>LIB Release - LIB OpenSSL</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release - LIB OpenSSL|x64">
<Configuration>LIB Release - LIB OpenSSL</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release|Win32">
<Configuration>LIB Release</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="LIB Release|x64">
<Configuration>LIB Release</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
</ItemGroup>
<PropertyGroup Label="Globals">
<ProjectGuid>{DA6F56B4-06A4-441D-AD70-AC5A7D51FADB}</ProjectGuid>
<RootNamespace>libcurl</RootNamespace>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|Win32'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|x64'" Label="Configuration">
<ConfigurationType>StaticLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<UseOfMfc>false</UseOfMfc>
VS projects: use Unicode for VC10+ All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
2019-04-02 07:11:34 -04:00
<CharacterSet>Unicode</CharacterSet>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
<ImportGroup Label="ExtensionSettings">
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
</ImportGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
<_ProjectFileVersion>10.0.30319.1</_ProjectFileVersion>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'">false</LinkIncremental>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'">false</LinkIncremental>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release|Win32'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release|Win32'">false</LinkIncremental>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|Win32'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release|x64'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release|x64'">false</LinkIncremental>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|x64'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug|Win32'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug|x64'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release|Win32'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release|x64'">$(OutDir)lib\</IntDir>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|Win32'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|Win32'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|x64'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|x64'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'">false</LinkIncremental>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'">false</LinkIncremental>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|Win32'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|Win32'">false</LinkIncremental>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|Win32'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|x64'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|x64'">false</LinkIncremental>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|x64'">false</LinkIncremental>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|Win32'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|Win32'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|x64'">$(OutDir)lib\</IntDir>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|x64'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|Win32'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|x64'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|Win32'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|Win32'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|x64'">$(OutDir)lib\</IntDir>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|x64'">$(OutDir)lib\</IntDir>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|x64'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|Win32'">..\..\..\..\build\Win32\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|Win32'">$(OutDir)lib\</IntDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|x64'">..\..\..\..\build\Win64\VC11\$(Configuration)\</OutDir>
<IntDir Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|x64'">$(OutDir)lib\</IntDir>
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'">$(ProjectName)d</TargetName>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'">$(ProjectName)d</TargetName>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'">$(ProjectName)d</TargetName>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'">$(ProjectName)d</TargetName>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug|Win32'">$(ProjectName)d</TargetName>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|Win32'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug|x64'">$(ProjectName)d</TargetName>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|x64'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|Win32'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|x64'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|x64'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|Win32'">$(ProjectName)d</TargetName>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|x64'">$(ProjectName)d</TargetName>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|x64'">$(ProjectName)d</TargetName>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|Win32'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|x64'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32'">$(ProjectName)d</TargetName>
<TargetName Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|x64'">$(ProjectName)d</TargetName>
</PropertyGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug|Win32'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|Win32'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WOLFSSL;USE_IPV6;WOLFSSL_DLL;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;wolfssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\wolfssl\build\Win32\VC11\DLL Debug;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug|x64'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL wolfSSL|x64'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WOLFSSL;USE_IPV6;WOLFSSL_DLL;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;wolfssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\wolfssl\build\Win64\VC11\DLL Debug;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release|Win32'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|Win32'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_WOLFSSL;USE_IPV6;WOLFSSL_DLL;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;wolfssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\wolfssl\build\Win32\VC11\DLL Release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX86</TargetMachine>
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release|x64'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL wolfSSL|x64'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_WOLFSSL;USE_IPV6;WOLFSSL_DLL;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
<AdditionalDependencies>ws2_32.lib;wldap32.lib;wolfssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\wolfssl\build\Win64\VC11\DLL Release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX64</TargetMachine>
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WOLFSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB wolfSSL|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WOLFSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WOLFSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB wolfSSL|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\wolfssl;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
projects: Fix Visual Studio wolfSSL configurations - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
2019-11-18 18:42:34 -05:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WOLFSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added wolfSSL configurations to VC10+ project files URL: https://github.com/bagder/curl/pull/174
2015-08-06 02:43:21 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|Win32'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win32\VC11\DLL Debug;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL|x64'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win64\VC11\DLL Debug;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|Win32'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Release\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win32\VC11\DLL Release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL|x64'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Release\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win64\VC11\DLL Release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|Win32'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;normaliz.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI|x64'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL Windows SSPI - DLL WinIDN|x64'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;normaliz.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<GenerateDebugInformation>true</GenerateDebugInformation>
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|Win32'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|Win32'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;normaliz.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI|x64'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL Windows SSPI - DLL WinIDN|x64'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
<AdditionalDependencies>ws2_32.lib;wldap32.lib;crypt32.lib;normaliz.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;libssh2d.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win32\VC11\DLL Debug;..\..\..\..\..\libssh2\build\Win32\VC11\DLL Debug;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Debug - DLL OpenSSL - DLL LibSSH2|x64'">
<Midl>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;libssh2d.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win64\VC11\DLL Debug;..\..\..\..\..\libssh2\build\Win64\VC11\DLL Debug;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<GenerateDebugInformation>true</GenerateDebugInformation>
build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output files Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
2014-05-28 16:46:57 -04:00
<ProgramDatabaseFile>$(TargetDir)$(TargetName).pdb</ProgramDatabaseFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|Win32'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>Win32</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Release\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;libssh2.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win32\VC11\DLL Release;..\..\..\..\..\libssh2\build\Win32\VC11\DLL Release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<ManifestFile>$(IntDir)$(TargetFileName).intermediate.manifest</ManifestFile>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='DLL Release - DLL OpenSSL - DLL LibSSH2|x64'">
<Midl>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<MkTypLibCompatible>true</MkTypLibCompatible>
<TargetEnvironment>X64</TargetEnvironment>
<TypeLibraryName>$(OutDir)$(ProjectName).tlb</TypeLibraryName>
<HeaderFileName>
</HeaderFileName>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Release\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Link>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalDependencies>crypt32.lib;ws2_32.lib;wldap32.lib;libcrypto.lib;libssl.lib;libssh2.lib;%(AdditionalDependencies)</AdditionalDependencies>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<AdditionalLibraryDirectories>..\..\..\..\..\openssl\build\Win64\VC11\DLL Release;..\..\..\..\..\libssh2\build\Win64\VC11\DLL Release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
build: Use $(TargetDir) and $(TargetName) macros for VC .lib output files As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
2014-05-28 17:12:44 -04:00
<ImportLibrary>$(TargetDir)$(TargetName).lib</ImportLibrary>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL OpenSSL - DLL LibSSH2|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Debug\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - DLL Windows SSPI - DLL WinIDN|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\LIB Debug\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\LIB Debug\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\LIB Debug\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Debug - LIB OpenSSL - LIB LibSSH2|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>Disabled</Optimization>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\LIB Debug\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Release\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Release\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\DLL Release\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL OpenSSL - DLL LibSSH2|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\DLL Release\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - DLL Windows SSPI - DLL WinIDN|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;USE_IPV6;WANT_IDN_PROTOTYPES;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added WinIDN build configuration options Added initial support for WinIDN build configurations to the VC10+ project files.
2014-09-19 07:43:10 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\LIB Release\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\LIB Release\include;..\..\..\..\..\openssl\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_IPV6;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win32\VC11\LIB Release\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX86</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='LIB Release - LIB OpenSSL - LIB LibSSH2|x64'">
<Midl>
<TargetEnvironment>X64</TargetEnvironment>
</Midl>
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<InlineFunctionExpansion>OnlyExplicitInline</InlineFunctionExpansion>
projects: Update VS projects for OpenSSL 1.1.x - Update VS project templates to use the OpenSSL lib names and include directories for OpenSSL 1.1.x. This change means the VS project files will now build only with OpenSSL 1.1.x when an OpenSSL configuration is chosen. Prior to this change the project files built only with OpenSSL 1.0.x (end-of-life) when an OpenSSL configuration was chosen. The template changes in this commit were made by script: libeay32.lib => libcrypto.lib ssleay32.lib => libssl.lib ..\..\..\..\..\openssl\inc32 => ..\..\..\..\..\openssl\include And since the output directory now contains the includes it's prepended: ..\..\..\..\..\openssl\build\Win{32,64}\VC{6..15}\{DLL,LIB} {Debug,Release}\include - Change build-openssl.bat to copy the build's include directory to the output directory (as seen above). Each build has its own opensslconf.h which is different so we can't just include the source include directory any longer. Note the include directory in the output directory is a full copy from the build so technically we don't need to include the OpenSSL source include directory in the template. However, I left it last in case the user made a custom OpenSSL build using the old method which would put opensslconf in the OpenSSL source include directory. - Change build-openssl.bat to use a temporary install directory that is different from the temporary build directory. For OpenSSL 1.1.x the temporary paths must be separate not a descendant of the other, otherwise pdb files will be lost between builds. Ref: https://curl.se/mail/lib-2018-10/0049.html Ref: https://gist.github.com/jay/125191c35bbeb894444eff827651f755 Ref; https://github.com/openssl/openssl/issues/10005 Fixes https://github.com/curl/curl/issues/984 Closes https://github.com/curl/curl/pull/6675
2021-03-01 03:20:58 -05:00
<AdditionalIncludeDirectories>..\..\..\..\include;..\..\..\..\lib;..\..\..\..\..\openssl\include\..\build\Win64\VC11\LIB Release\include;..\..\..\..\..\openssl\include;..\..\..\..\..\libssh2\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
VS projects: add USE_IPV6 The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
2018-10-17 11:34:56 -04:00
<PreprocessorDefinitions>NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;USE_IPV6;HAVE_LIBSSH2_H;%(PreprocessorDefinitions)</PreprocessorDefinitions>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
<StringPooling>true</StringPooling>
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
build: Changed the Visual Studio projects warning level from 3 to 4 After squashing most of our compiler warnings, up'ed the default warning level from 3 to 4 in order to increase the likelyhood of catching future warnings.
2016-04-01 15:39:34 -04:00
<WarningLevel>Level4</WarningLevel>
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
</ClCompile>
<ResourceCompile>
<PreprocessorDefinitions>NDEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
<Culture>0x0409</Culture>
</ResourceCompile>
<Lib>
<OutputFile>$(OutDir)$(TargetName)$(TargetExt)</OutputFile>
<TargetMachine>MachineX64</TargetMachine>
</Lib>
</ItemDefinitionGroup>
<ItemGroup>
CURL_LIB_C_FILES
build: Updated all makefiles and project files for the new vauth directory Updated the makefiles and Visual Studio project files to support moving the authentication code to the new lib/vauth directory that was started in commit 0d04e859e1.
2015-09-12 06:14:14 -04:00
CURL_LIB_VAUTH_C_FILES
projects: Fix Visual Studio projects SSH builds - Generate VQUIC and VSSH filenames in Visual Studio project files. Prior to this change generated Visual Studio project configurations that enabled SSH did not build properly. Broken since SSH files were moved to lib/vssh 3 months ago in 5b2d703. Fixes https://github.com/curl/curl/issues/4492 Fixes https://github.com/curl/curl/issues/4630 Closes https://github.com/curl/curl/pull/4607
2019-11-17 03:08:40 -05:00
CURL_LIB_VQUIC_C_FILES
CURL_LIB_VSSH_C_FILES
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
CURL_LIB_VTLS_C_FILES
</ItemGroup>
<ItemGroup>
CURL_LIB_H_FILES
build: Updated all makefiles and project files for the new vauth directory Updated the makefiles and Visual Studio project files to support moving the authentication code to the new lib/vauth directory that was started in commit 0d04e859e1.
2015-09-12 06:14:14 -04:00
CURL_LIB_VAUTH_H_FILES
projects: Fix Visual Studio projects SSH builds - Generate VQUIC and VSSH filenames in Visual Studio project files. Prior to this change generated Visual Studio project configurations that enabled SSH did not build properly. Broken since SSH files were moved to lib/vssh 3 months ago in 5b2d703. Fixes https://github.com/curl/curl/issues/4492 Fixes https://github.com/curl/curl/issues/4630 Closes https://github.com/curl/curl/pull/4607
2019-11-17 03:08:40 -05:00
CURL_LIB_VQUIC_H_FILES
CURL_LIB_VSSH_H_FILES
build: Added Visual Studio 2012 (VC11) project files Carrying on from commit 11025613b9 added VC11 project files which are capable of supporting side-by-side compilation, 32-bit and 64-bit builds as well as support for some of the third-party libraries curl uses.
2014-04-18 05:24:20 -04:00
CURL_LIB_VTLS_H_FILES
</ItemGroup>
<ItemGroup>
CURL_LIB_RC_FILES
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
</Project>
Reference in New Issue Copy Permalink