summaryrefslogtreecommitdiff
path: root/projects/Windows
Commit message (Collapse)AuthorAgeFilesLines
* projects: Update VS projects for OpenSSL 1.1.xJay Satiro2021-03-0320-432/+432
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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
* projects: Add crypt32.lib to dependencies for all OpenSSL configsJay Satiro2020-06-0420-144/+144
| | | | | | | | | | | | | Windows project configurations that use OpenSSL with USE_WIN32_CRYPTO need crypt32. Follow-up to 148534d which added CURLSSLOPT_NATIVE_CA for 7.71.0. The changes that are in this commit were made by script. Ref: https://gist.github.com/jay/a1861b50ecce2b32931237180f856e28 Closes https://github.com/curl/curl/pull/5516
* projects: Fix Visual Studio projects SSH buildsJay Satiro2019-11-2410-0/+136
| | | | | | | | | | | | - 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
* projects: Fix Visual Studio wolfSSL configurationsJay Satiro2019-11-185-40/+40
| | | | | | | | | | | - s/USE_CYASSL/USE_WOLFSSL/ - Remove old compatibility macros. Follow-up to 1c6c59a from several months ago when CyaSSL named symbols were renamed to wolfSSL. The wolfSSL library was formerly named CyaSSL and we kept using their old name for compatibility reasons, until earlier this year.
* VS projects: use Unicode for VC10+Marcel Raad2019-04-0410-560/+560
| | | | | | | | | | | | | All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720
* VC15 project: remove MinimalRebuildMarcel Raad2019-04-011-28/+0
| | | | | | Already done in commit d5cfefd0ea8e331b884186bff484210fad36e345 for the library project, but I forgot the tool project template. Now also removed for that.
* VS projects: fix build warningMarcel Raad2019-01-061-28/+0
| | | | | | | | | | | | Starting with Visual Studio 2017 Update 9, Visual Studio doesn't like the MinimalRebuild option anymore and warns: cl : Command line warning D9035: option 'Gm' has been deprecated and will be removed in a future release The option can be safely removed so that the default is used. Closes https://github.com/curl/curl/pull/3425
* VS projects: add USE_IPV6Marcel Raad2018-10-196-328/+328
| | | | | | | The Visual Studio builds didn't use IPv6. Add it to all projects since Visual Studio 2008, which is verified to build via AppVeyor. Closes https://github.com/curl/curl/pull/3137
* build: open VC15 projects with VS 2017Marcel Raad2018-01-293-3/+3
| | | | | Previously, they were opened with Visual Studio 2015 by default, which cannot build them.
* build: Added Visual Studio 2017 project filesSteve Holme2017-12-2210-0/+5807
|
* build: check out *.sln files with Windows line endingsMarcel Raad2017-08-101-0/+1
| | | | | | | | Visual Studio doesn't like LF line endings in solution files and always converts them to CRLF when doing changes to the solution. Notably, this affects the solutions in the release archive. Closes https://github.com/curl/curl/pull/1746
* VC: Add crypt32.lib to Visual Sudio project template filesJoel Depooter2016-06-2218-128/+128
| | | | Closes #854
* build: Changed the Visual Studio projects warning level from 3 to 4Steve Holme2016-04-0118-832/+832
| | | | | | 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.
* .gitignore: Added new VC14 SQLite based program database filesSteve Holme2016-04-013-2/+5
|
* build: Updated all makefiles and project files for the new vauth directorySteve Holme2016-03-259-0/+66
| | | | | | 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.
* build: Added missing Visual Studio filter files for VC10 onwardsSteve Holme2016-03-1916-8/+136
| | | | | | | | | | As these files don't need to contain references to the source files, although typically do, added basic files which only include three filters and don't require the project file generator to be modified. These files allow the source code to be viewed in the Solution Explorer in versions of Visual Studio from 2010 onwards in the same manner as previous versions did rather than one large view of files.
* .gitignore: Added *.VC.opendb and *.vcxproj.user files for VC14Steve Holme2016-03-053-0/+3
|
* projects/Windows/.gitignore: ignore generated files for releaseDaniel Stenberg2015-09-031-0/+6
|
* gitignore: Sort for readabilityJay Satiro2015-08-1816-27/+27
| | | | find . -name .gitignore -print0 | xargs -i -0 sort -o '{}' '{}'
* build: Added wolfSSL configurations to VC10+ project filesJay Satiro2015-08-0620-0/+3280
| | | | URL: https://github.com/bagder/curl/pull/174
* build: Added VC14 project filesSteve Holme2015-07-298-0/+4943
| | | | | Updates to Makefile.am for the generation of the project files in the tarball to follow.
* build: Fixed missing .opensdf files from VC10+ .gitignore filesSteve Holme2015-07-286-0/+6
|
* build: Use $(ProjectName) macro for curl.exe and curld.exe filenamesSteve Holme2015-07-287-288/+288
| | | | | | This wasn't possible with the old curlsrc project filenames, but like commit 2a615a2b64 and 11397eb6dd for libcurl use the built in Visual Studio macros for the output filenames.
* build: Renamed curl src Visual Studio project filesSteve Holme2015-07-2824-101/+101
| | | | | Following commit 957fcd9049 and in preparation for adding the VC14 project files renamed the curl source project files.
* build: Fix libcurl.sln erroneous mixed configurationsJay Satiro2015-03-275-44/+44
| | | | | Prior to this change some Release configurations had an active configuration assignment to their Debug counterpart.
* openssl: Removed use of USE_SSLEAY from the Visual Studio project filesSteve Holme2015-03-058-168/+168
| | | | | | In addition to commit 709cf76f6b, removed the USE_SSLEAY preprocessor variable from the Visual Studio project files as it isn't required anymore.
* build: Removed DataExecutionPrevention directive from VC9+ project filesSteve Holme2015-02-268-476/+0
| | | | | | | Removed the DataExecutionPrevention directive from the project files for Visual Studio 2008 and above. The XML value in the VC9 project files was set to "0" (Default) whilst the VC10+ project files contained an empty XML element.
* build: Use default RandomizedBaseAddress directive in VC9+ project filesSteve Holme2015-02-268-272/+0
| | | | | | | | | | Visual Studio 2008 introduced support for the address space layout randomization (ASLR) feature of Windows Vista. However, upgrading the VC8 project files to VC9 and above disabled this feature. Removed the RandomizedBaseAddress directive to enabled the default setting (/DYNAMICBASE). Note: This doesn't appear to have any negative impact when compiled and ran on Windows XP.
* build: Removed Visual Studio SuppressStartupBanner directive for VC8+Steve Holme2015-02-1410-1060/+0
| | | | | | | | Visual Studio 2005 and above defaults to disabling the startup banner for the Compiler, Linker and MIDL tools (with /NOLOGO). As such there is no need to explicitly set the SuppressStartupBanner directive, as this is a leftover from the VC7 and VC7.1 projects being upgraded to VC8 and above.
* build: Renamed top level Visual Studio solution filesSteve Holme2015-02-028-0/+0
| | | | | | | | | In preparation for adding the test suite and examples projects renamed the top level "all" solution files to better describe what they are. This will also enable us to use "curl" rather than "curlsrc" for the command line tool solution and project files, which will simplify some of the configuration.
* build: Enabled DEBUGBUILD in Visual Studio debug buildsSteve Holme2015-02-0216-336/+336
| | | | | | | | | | 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.
* build: Removed unused Visual Studio bscmake settingsSteve Holme2015-02-0210-1536/+0
|
* build: Removed WIN32 definition from the Visual Studio projectsSteve Holme2014-12-2416-553/+553
| | | | | As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
* build: Removed WIN64 definition from the libcurl Visual Studio projectsSteve Holme2014-12-245-121/+121
| | | | | | | | | | | | | | | | | | | | | Removed the WIN64 pre-processor definition from the libcurl project files as: * WIN64 is not used in our source code * The curl projects files don't define it * It isn't required by or used in the platform SDK * For backwards compatability curl_setup.h defines WIN32 * The compiler automatically defines _WIN64 for x64 builds Historically Visual Studio projects have defined WIN32, in addition to the compiler defined _WIN32 definition, and I had incorrectly changed that to WIN64 for the x64 libcurl builds but not in the curl projects. As such, it is questionable whether this should be defined or not. For more information see the following cache of a discussion that took place on the microsoft.public.vc.mfc newsgroup: http://www.tech-archive.net/Archive/VC/microsoft.public.vc.mfc/2008-06/msg00074.html
* build: Added WinIDN build configuration optionsSteve Holme2014-11-022-0/+226
| | | | Added support for WinIDN build configurations to the VC6 project files.
* build: Added WinIDN build configuration optionsSteve Holme2014-11-0210-48/+954
| | | | | Added support for WinIDN build configurations to the VC7 and VC7.1 project files.
* build: Fixed the pre-processor separator in Visual Studio project filesSteve Holme2014-11-024-64/+64
| | | | | | | | | | | | A left over from the VC6 project files, so mainly cosmetic in Visual Studio .NET as it can handle both comma and semi-colon characters for separating multiple pre-processor definitions. However, the IDE uses semi-colons if the value is edited, and as such, this may cause problems in future for anyone updating the files or merging patches. Used the Visual Studio IDE to correct the separator character.
* build: Added WinIDN build configuration optionsSteve Holme2014-10-2510-0/+2876
| | | | | Added support for WinIDN build configurations to the VC8 and VC9 project files.
* build: Added WinIDN build configuration optionsSteve Holme2014-09-1915-2/+2830
| | | | | Added initial support for WinIDN build configurations to the VC10+ project files.
* build: Removed unnecessary XML Documentation file directive from VC8 to VC12Steve Holme2014-07-175-200/+0
| | | | | | | | | | | | | | The curl tool project files for VC8 to VC12 would set this setting to $(IntDir) which is the Visual Studio default value. To avoid confusion when viewing settings from within Visual Studio and for consistency with the libcurl project files removed this setting. Conflicts: projects/Windows/VC10/src/curlsrc.tmpl projects/Windows/VC11/src/curlsrc.tmpl projects/Windows/VC12/src/curlsrc.tmpl projects/Windows/VC8/src/curlsrc.tmpl projects/Windows/VC9/src/curlsrc.tmpl
* build: Removed unnecessary Precompiled Header file directive in VC7 to VC12Steve Holme2014-07-177-240/+0
| | | | | | | | | | | | | | The curl tool project files for VC7 to VC12 would set this settings to $(IntDir)$(TargetName).pch which is the Visual Studio default value. To avoid confusion when viewing settings from within Visual Studio and for consistency with the libcurl project files removed this setting. Conflicts: projects/Windows/VC10/src/curlsrc.tmpl projects/Windows/VC11/src/curlsrc.tmpl projects/Windows/VC12/src/curlsrc.tmpl projects/Windows/VC8/src/curlsrc.tmpl projects/Windows/VC9/src/curlsrc.tmpl
* build: Removed unnecessary ASM and Object file directives in VC7 to VC12Steve Holme2014-07-177-480/+0
| | | | | | | The curl tool project files for VC7 to VC12 would set these settings to $(IntDir) which is the Visual Studio default value. To avoid confusion when viewing settings from within Visual Studio and for consistency with the libcurl project files removed these two settings.
* build: Fixed overridden compiler PDB settings in VC7 to VC12Steve Holme2014-07-127-240/+0
| | | | | | | | | | The curl tool project files for VC7 to VC12 would override the default setting with the output filename being the same as the linker PDB file. As such the compiler file would be overwritten with the linker file for all debug builds. To avoid this overwrite and for consistency with the libcurl project files, removed the setting to force the default filename to be used.
* build: Fixed Visual Studio static OpenSSL builds following commit c50ce85918Steve Holme2014-06-058-56/+56
|
* build: Use $(TargetDir) and $(TargetName) macros for VC .lib output filesSteve Holme2014-05-287-96/+96
| | | | | | As with commit 11397eb6dd, use $(TargetDir) and $(TargetName) for the Import Library output rather than $(OutDir)\$(ProjectName)d.lib and $(OutDir)\$(ProjectName).lib.
* build: Use $(TargetDir) and $(TargetName) macros for VC .pdb output filesSteve Holme2014-05-287-48/+48
| | | | | | Like with the curl tool project files use $(TargetDir)$(TargetName).pdb rather than $(OutDir)$(ProjectName)d.pdb for the Program Database File output.
* build: Use CURLX_* file lists for Visual Studio curl tool project generationSteve Holme2014-05-228-210/+16
|
* build: Fixed incorrect reference to curl_setup.h in Visual Studio filesSteve Holme2014-05-228-19/+19
| | | | Fixed a copy / paste error from my 2011 project files.
* build: Fixed file format version number in VC12 solution filesSteve Holme2014-05-063-3/+3
| | | | | | | | | | | | | | Unlike previous versions of Visual Studio the VC12 solution file format does not increment the format version number, but instead, only changes the version comment text. This incorrectly set version number would cause problems for any third party piece of software that would read the solution file expecting the version number to be 12.00 and found it to be 13.00, such as some build accelerators. Verified against a freshly created solution file which was generated with VC12.
* build: Added Visual Studio 2003 .NET (VC7.1) project filesSteve Holme2014-05-018-0/+2621
| | | | | | 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.