moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-14 13:35:03 -05:00
Code Issues Releases Wiki Activity
dd81489db9
curl/projects/Windows/VC7.1/lib/libcurl.tmpl

1330 lines
40 KiB
Cheetah
Raw Normal View History

build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<?xml version="1.0" encoding="Windows-1252"?>
<VisualStudioProject
ProjectType="Visual C++"
Version="7.10"
Name="libcurl"
ProjectGUID="{DA6F56B4-06A4-441D-AD70-AC5A7D51FADB}"
SccProjectName=""
SccLocalPath="">
<Platforms>
<Platform
Name="Win32"/>
</Platforms>
<Configurations>
<Configuration
Name="DLL Release - DLL OpenSSL - DLL LibSSH2|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Release\include,..\..\..\..\..\openssl\include,..\..\..\..\..\libssh2\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;USE_OPENSSL;USE_LIBSSH2;HAVE_LIBSSH2_H"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
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 wldap32.lib ws2_32.lib libcrypto.lib libssl.lib libssh2.lib"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
OutputFile="$(OutDir)\$(ProjectName).dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
AdditionalLibraryDirectories="..\..\..\..\..\openssl\build\Win32\VC7.1\DLL Release,..\..\..\..\..\libssh2\build\Win32\VC7.1\DLL Release"
SetChecksum="TRUE"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="NDEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Debug - DLL OpenSSL|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Debug\include,..\..\..\..\..\openssl\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_OPENSSL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
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 wldap32.lib ws2_32.lib libcrypto.lib libssl.lib"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
OutputFile="$(OutDir)\$(ProjectName)d.dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
AdditionalLibraryDirectories="..\..\..\..\..\openssl\build\Win32\VC7.1\DLL Debug"
GenerateDebugInformation="TRUE"
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"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="_DEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Debug|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Enabled DEBUGBUILD in Visual Studio debug builds Defined the DEBUGBUILD pre-processor variable to allow extra logging, which is particularly useful in debug builds, as we use this and Visual Studio typically uses _DEBUG. We could define DEBUBBUILD, in curl_setup.h, when _MSC_VER and _DEBUG is defined but that would also affect the makefile based builds which we probably don't want to do.
2015-02-01 16:02:57 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
AdditionalDependencies="wldap32.lib ws2_32.lib"
OutputFile="$(OutDir)\$(ProjectName)d.dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
GenerateDebugInformation="TRUE"
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"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="_DEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release - DLL OpenSSL|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Release\include,..\..\..\..\..\openssl\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug - DLL OpenSSL - DLL LibSSH2|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Debug\include,..\..\..\..\..\openssl\include,..\..\..\..\..\libssh2\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;HAVE_LIBSSH2_H"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Release|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Removed WIN32 definition from the Visual Studio projects As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
2014-12-24 09:56:59 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
AdditionalDependencies="wldap32.lib ws2_32.lib"
OutputFile="$(OutDir)\$(ProjectName).dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
SetChecksum="TRUE"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="NDEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug - LIB OpenSSL - LIB LibSSH2|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\LIB Debug\include,..\..\..\..\..\openssl\include,..\..\..\..\..\libssh2\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;HAVE_LIBSSH2_H"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug - DLL Windows SSPI|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Enabled DEBUGBUILD in Visual Studio debug builds Defined the DEBUGBUILD pre-processor variable to allow extra logging, which is particularly useful in debug builds, as we use this and Visual Studio typically uses _DEBUG. We could define DEBUBBUILD, in curl_setup.h, when _MSC_VER and _DEBUG is defined but that would also affect the makefile based builds which we probably don't want to do.
2015-02-01 16:02:57 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug - DLL OpenSSL|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Debug\include,..\..\..\..\..\openssl\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Release - DLL Windows SSPI|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Removed WIN32 definition from the Visual Studio projects As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
2014-12-24 09:56:59 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;USE_WINDOWS_SSPI;USE_SCHANNEL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
AdditionalDependencies="wldap32.lib ws2_32.lib crypt32.lib"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
OutputFile="$(OutDir)\$(ProjectName).dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
SetChecksum="TRUE"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="NDEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Debug - DLL Windows SSPI|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Enabled DEBUGBUILD in Visual Studio debug builds Defined the DEBUGBUILD pre-processor variable to allow extra logging, which is particularly useful in debug builds, as we use this and Visual Studio typically uses _DEBUG. We could define DEBUBBUILD, in curl_setup.h, when _MSC_VER and _DEBUG is defined but that would also affect the makefile based builds which we probably don't want to do.
2015-02-01 16:02:57 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WINDOWS_SSPI;USE_SCHANNEL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
AdditionalDependencies="wldap32.lib ws2_32.lib crypt32.lib"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
OutputFile="$(OutDir)\$(ProjectName)d.dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
GenerateDebugInformation="TRUE"
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"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="_DEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release - DLL Windows SSPI|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Removed WIN32 definition from the Visual Studio projects As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
2014-12-24 09:56:59 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Release - DLL OpenSSL|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Release\include,..\..\..\..\..\openssl\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;USE_OPENSSL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
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 wldap32.lib ws2_32.lib libcrypto.lib libssl.lib"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
OutputFile="$(OutDir)\$(ProjectName).dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
AdditionalLibraryDirectories="..\..\..\..\..\openssl\build\Win32\VC7.1\DLL Release"
SetChecksum="TRUE"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="NDEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release - LIB OpenSSL|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\LIB Release\include,..\..\..\..\..\openssl\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Removed WIN32 definition from the Visual Studio projects As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
2014-12-24 09:56:59 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release - DLL OpenSSL - DLL LibSSH2|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Release\include,..\..\..\..\..\openssl\include,..\..\..\..\..\libssh2\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;HAVE_LIBSSH2_H"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release - LIB OpenSSL - LIB LibSSH2|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\LIB Release\include,..\..\..\..\..\openssl\include,..\..\..\..\..\libssh2\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_OPENSSL;USE_LIBSSH2;HAVE_LIBSSH2_H"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Enabled DEBUGBUILD in Visual Studio debug builds Defined the DEBUGBUILD pre-processor variable to allow extra logging, which is particularly useful in debug builds, as we use this and Visual Studio typically uses _DEBUG. We could define DEBUBBUILD, in curl_setup.h, when _MSC_VER and _DEBUG is defined but that would also affect the makefile based builds which we probably don't want to do.
2015-02-01 16:02:57 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Debug - DLL OpenSSL - DLL LibSSH2|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\DLL Debug\include,..\..\..\..\..\openssl\include,..\..\..\..\..\libssh2\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_OPENSSL;USE_LIBSSH2;HAVE_LIBSSH2_H"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
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 wldap32.lib ws2_32.lib libcrypto.lib libssl.lib libssh2d.lib"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
OutputFile="$(OutDir)\$(ProjectName)d.dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
AdditionalLibraryDirectories="..\..\..\..\..\openssl\build\Win32\VC7.1\DLL Debug,..\..\..\..\..\libssh2\build\Win32\VC7.1\DLL Debug"
GenerateDebugInformation="TRUE"
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"
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"/>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="_DEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug - LIB OpenSSL|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
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="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib,..\..\..\..\..\openssl\include\..\build\Win32\VC7.1\LIB Debug\include,..\..\..\..\..\openssl\include"
openssl: Removed use of USE_SSLEAY from the Visual Studio project files In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
2015-03-05 15:47:14 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_OPENSSL"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
<Configuration
Name="DLL Debug - DLL Windows SSPI - DLL WinIDN|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Enabled DEBUGBUILD in Visual Studio debug builds Defined the DEBUGBUILD pre-processor variable to allow extra logging, which is particularly useful in debug builds, as we use this and Visual Studio typically uses _DEBUG. We could define DEBUBBUILD, in curl_setup.h, when _MSC_VER and _DEBUG is defined but that would also affect the makefile based builds which we probably don't want to do.
2015-02-01 16:02:57 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;WANT_IDN_PROTOTYPES"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
AdditionalDependencies="normaliz.lib wldap32.lib ws2_32.lib crypt32.lib"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
OutputFile="$(OutDir)\$(ProjectName)d.dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
GenerateDebugInformation="TRUE"
ProgramDatabaseFile="$(TargetDir)$(TargetName).pdb"
ImportLibrary="$(TargetDir)$(TargetName).lib"/>
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="_DEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="DLL Release - DLL Windows SSPI - DLL WinIDN|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="2"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Removed WIN32 definition from the Visual Studio projects As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
2014-12-24 09:56:59 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;WANT_IDN_PROTOTYPES"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLinkerTool"
AdditionalOptions="/MACHINE:I386 /FIXED:NO"
VC: Add crypt32.lib to Visual Sudio project template files Closes #854
2016-06-01 19:29:32 -04:00
AdditionalDependencies="normaliz.lib wldap32.lib ws2_32.lib crypt32.lib"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
OutputFile="$(OutDir)\$(ProjectName).dll"
LinkIncremental="1"
SuppressStartupBanner="TRUE"
SetChecksum="TRUE"
ImportLibrary="$(TargetDir)$(TargetName).lib"/>
<Tool
Name="VCMIDLTool"
PreprocessorDefinitions="NDEBUG"
SuppressStartupBanner="TRUE"
TargetEnvironment="1"
TypeLibraryName="$(OutDir)\$(ProjectName).tlb"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCWebDeploymentTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Debug - DLL Windows SSPI - DLL WinIDN|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
Optimization="0"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Enabled DEBUGBUILD in Visual Studio debug builds Defined the DEBUGBUILD pre-processor variable to allow extra logging, which is particularly useful in debug builds, as we use this and Visual Studio typically uses _DEBUG. We could define DEBUBBUILD, in curl_setup.h, when _MSC_VER and _DEBUG is defined but that would also affect the makefile based builds which we probably don't want to do.
2015-02-01 16:02:57 -05:00
PreprocessorDefinitions="_DEBUG;BUILDING_LIBCURL;DEBUGBUILD;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;WANT_IDN_PROTOTYPES"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
BasicRuntimeChecks="3"
RuntimeLibrary="3"
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="4"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
SuppressStartupBanner="TRUE"
DebugInformationFormat="3"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName)d.lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_DEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
<Configuration
Name="LIB Release - DLL Windows SSPI - DLL WinIDN|Win32"
OutputDirectory=".\..\..\..\..\build\Win32\VC7.1\$(ConfigurationName)"
IntermediateDirectory="$(OutDir)\lib"
ConfigurationType="4"
UseOfMFC="0"
ATLMinimizesCRunTimeLibraryUsage="FALSE">
<Tool
Name="VCCLCompilerTool"
AdditionalOptions="/EHsc "
InlineFunctionExpansion="1"
AdditionalIncludeDirectories="$(ProgramFiles)\Microsoft Platform SDK\Include,..\..\..\..\include,..\..\..\..\lib"
build: Removed WIN32 definition from the Visual Studio projects As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
2014-12-24 09:56:59 -05:00
PreprocessorDefinitions="NDEBUG;BUILDING_LIBCURL;CURL_STATICLIB;USE_WINDOWS_SSPI;USE_SCHANNEL;USE_WIN32_IDN;WANT_IDN_PROTOTYPES"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
StringPooling="TRUE"
RuntimeLibrary="2"
EnableFunctionLevelLinking="TRUE"
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="4"
build: Added WinIDN build configuration options Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
2014-11-02 11:23:48 -05:00
SuppressStartupBanner="TRUE"
CompileAs="0"/>
<Tool
Name="VCCustomBuildTool"/>
<Tool
Name="VCLibrarianTool"
AdditionalOptions="/machine:I386 "
OutputFile="$(OutDir)\$(ProjectName).lib"
SuppressStartupBanner="TRUE"/>
<Tool
Name="VCMIDLTool"/>
<Tool
Name="VCPostBuildEventTool"/>
<Tool
Name="VCPreBuildEventTool"/>
<Tool
Name="VCPreLinkEventTool"/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="NDEBUG"
Culture="1033"/>
<Tool
Name="VCWebServiceProxyGeneratorTool"/>
<Tool
Name="VCXMLDataGeneratorTool"/>
<Tool
Name="VCManagedWrapperGeneratorTool"/>
<Tool
Name="VCAuxiliaryManagedWrapperGeneratorTool"/>
</Configuration>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
</Configurations>
<References>
</References>
<Files>
<Filter
Name="Source Files"
Filter="">
CURL_LIB_C_FILES
</Filter>
<Filter
Name="Header Files"
Filter="">
CURL_LIB_H_FILES
</Filter>
<Filter
Name="Resource Files"
Filter="">
CURL_LIB_RC_FILES
</Filter>
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
<Filter
Name="vauth"
Filter="">
<Filter
Name="Source Files"
Filter="">
CURL_LIB_VAUTH_C_FILES
</Filter>
<Filter
Name="Header Files"
Filter="">
CURL_LIB_VAUTH_H_FILES
</Filter>
</Filter>
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
<Filter
Name="vquic"
Filter="">
<Filter
Name="Source Files"
Filter="">
CURL_LIB_VQUIC_C_FILES
</Filter>
<Filter
Name="Header Files"
Filter="">
CURL_LIB_VQUIC_H_FILES
</Filter>
</Filter>
<Filter
Name="vssh"
Filter="">
<Filter
Name="Source Files"
Filter="">
CURL_LIB_VSSH_C_FILES
</Filter>
<Filter
Name="Header Files"
Filter="">
CURL_LIB_VSSH_H_FILES
</Filter>
</Filter>
build: Added Visual Studio 2003 .NET (VC7.1) project files Carrying on from commit 11025613b9 added VC7.1 project files which are capable of supporting side-by-side compilation, as well as support for some of the third-party libraries curl uses.
2014-05-01 15:29:34 -04:00
<Filter
Name="vtls"
Filter="">
<Filter
Name="Source Files"
Filter="">
CURL_LIB_VTLS_C_FILES
</Filter>
<Filter
Name="Header Files"
Filter="">
CURL_LIB_VTLS_H_FILES
</Filter>
</Filter>
</Files>
<Globals>
</Globals>
</VisualStudioProject>
Reference in New Issue Copy Permalink