romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-04-14 22:21:41 +03:00
Code Issues Projects Releases Packages Wiki Activity

projects/Windows: remove wolfSSL from legacy projects

Browse source 
- Remove wolfSSL from the legacy projects for Visual Studio 2010 - 2013.

It's no longer possible to maintain the custom build configuration of
wolfSSL for these old versions of Visual Studio.

Note support for wolfSSL was recently added to the winbuild build system
in 4de627ab and the user could possibly make their own wolfSSL build and
attempt to link it using an old version of Visual Studio that way.

Ref: https://gist.github.com/jay/5f6d8d5ba15c12c7457e3216a94da72d

Closes https://github.com/curl/curl/pull/15468
This commit is contained in:
Jay Satiro 2024-11-01 04:24:26 -04:00
parent 18650ea011
commit 440bf8dcca
21 changed files with 17 additions and 3285 deletions
Download patch file Download diff file Expand all files Collapse all files

38
projects/README.md
View file

@ -16,6 +16,9 @@ You will need to generate the project files before using them. Please run
To generate project files for recent versions of Visual Studio instead, use
cmake. Refer to INSTALL-CMAKE in the docs directory.
Another way to build curl using Visual Studio is without project files. Refer
to README in the winbuild directory.
## Directory Structure
The following directory structure is used for the legacy project files:
@ -39,8 +42,8 @@ a library is being compiled against dynamic runtime libraries.
## Dependencies
The projects files also support build configurations that require third party
dependencies such as OpenSSL, wolfSSL and libssh2. If you wish to support
these, you will also need to download and compile those libraries as well.
dependencies such as OpenSSL and libssh2. If you wish to support these, you
will also need to download and compile those libraries as well.
To support compilation of these libraries using different versions of
compilers, the following directory structure has been used for both the output
@ -67,10 +70,9 @@ of curl and libcurl as well as these dependencies.
|_VC <version>
|_<configuration>
As OpenSSL and wolfSSL don't support side-by-side compilation when using
different versions of Visual Studio, build helper batch files have been
provided to assist with this. Please run `build-openssl -help` and/or
`build-wolfssl -help` for usage details.
As OpenSSL doesn't support side-by-side compilation when using different
versions of Visual Studio, a helper batch file has been provided to assist with
this. Please run `build-openssl -help` for usage details.
## Building with Visual C++
@ -97,7 +99,7 @@ use `VC10\curl-all.sln` to build curl and libcurl.
## Running DLL based configurations
If you are a developer and plan to run the curl tool from Visual Studio with
any third-party libraries (such as OpenSSL, wolfSSL or libssh2) then you will
any third-party libraries (such as OpenSSL or libssh2) then you will
need to add the search path of these DLLs to the configuration's PATH
environment. To do that:
@ -119,16 +121,6 @@ DLL Debug - DLL OpenSSL (x64):
PATH=..\..\..\..\..\openssl\build\Win64\VC10\DLL Debug;C:\Windows\System32;
C:\Windows;C:\Windows\System32\Wbem
DLL Debug - DLL wolfSSL (Win32):
PATH=..\..\..\..\..\wolfssl\build\Win32\VC10\DLL Debug;C:\Windows\System32;
C:\Windows;C:\Windows\System32\Wbem
DLL Debug - DLL wolfSSL (x64):
PATH=..\..\..\..\..\wolfssl\build\Win64\VC10\DLL Debug;C:\Windows\System32;
C:\Windows;C:\Windows\System32\Wbem
If you are using a configuration that uses multiple third-party library DLLs
(such as DLL Debug - DLL OpenSSL - DLL libssh2) then 'Path to DLL' will need
to contain the path to both of these.
@ -152,9 +144,9 @@ files that Visual Studio uses.
## Legacy Windows and SSL
Some of the project configurations allow the use of Schannel, the native SSL
library in Windows which forms part of Windows SSPI. However, Schannel in
Windows <= XP is unable to connect to servers that no longer support the
legacy handshakes and algorithms used by those versions. If you will be using
curl in one of those earlier versions of Windows you should choose another SSL
backend such as OpenSSL.
Some of the project configurations use Schannel (Windows SSPI), the native SSL
library that comes with the Windows OS. Schannel in Windows 8 and earlier is
not able to connect to servers that no longer support the legacy handshakes
and algorithms used by those versions. If you will be using curl in one of
those earlier versions of Windows you should choose another SSL backend like
OpenSSL.