summaryrefslogtreecommitdiff
path: root/projects/README
diff options
context:
space:
mode:
Diffstat (limited to 'projects/README')
-rw-r--r--projects/README58
1 files changed, 54 insertions, 4 deletions
diff --git a/projects/README b/projects/README
index b45d78397..e5fd019de 100644
--- a/projects/README
+++ b/projects/README
@@ -68,16 +68,16 @@ Building with Visual C++
If you are building with VC6 then you will also need the February 2003
Edition of the Windows Platform SDK which can be downloaded from:
- http://www.microsoft.com/en-us/download/details.aspx?id=12261
+ https://www.microsoft.com/en-us/download/details.aspx?id=12261
If you require support for Internationalized Domain Names via Windows IDN
then you will need either:
* Microsoft Internationalized Domain Name (IDN) Mitigation APIs:
- http://www.microsoft.com/en-us/download/details.aspx?id=734
+ https://www.microsoft.com/en-us/download/details.aspx?id=734
* Microsoft Windows SDK Update for Windows Vista:
- http://www.microsoft.com/en-us/download/details.aspx?id=23719
+ https://www.microsoft.com/en-us/download/details.aspx?id=23719
* Microsoft Visual Studio 2010 or above
@@ -88,6 +88,46 @@ Building with Visual C++
well as a configuration that includes both, it is recommend that you use the
all-in-one configuration.
+Running DLL based configurations
+================================
+
+ If you are a developer and plan to run the curl tool from Visual Studio (eg
+ you are debugging) with any third-party libraries (such as OpenSSL, wolfSSL
+ or LibSSH2) then you will need to add the search path of these DLLs to the
+ configuration's PATH environment. To do that:
+
+ * Open the 'curl-all.sln' or 'curl.sln' solutions
+
+ * Right-click on the 'curl' project and select Properties
+
+ * Navigate to 'Configuration Properties > Debugging > Environment'
+
+ * Add PATH='Path to DLL';C:\Windows\system32;C:\Windows;
+ C:\Windows\System32\Wbem
+
+ ... where 'Path to DLL` is the configuration specific path. For example the
+ following configurations in Visual Studio 2010 might be:
+
+ DLL Debug - DLL OpenSSL (Win32):
+ PATH=..\..\..\..\..\openssl\build\Win32\VC10\DLL Debug;C:\Windows\system32;
+ C:\Windows;C:\Windows\System32\Wbem
+
+ 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.
+
Notes
=====
@@ -110,6 +150,16 @@ Notes
stored in the git repositoty) will need to be modified rather than the
generated project files that Visual Studio uses.
+Legacy Windows and SSL
+======================
+
+ Some of the project configurations allow the use of WinSSL (specifically
+ SChannel from Windows SSPI), the native SSL library in Windows. However,
+ WinSSL 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.
+
TODO
====
@@ -118,8 +168,8 @@ TODO
* Support zlib
* Use of static runtime libraries
- * Generate *.vcxproj.filters files for VC10, VC11 and VC12
* Add the Test Suite components
* Support for other development IDEs
+ * Add PATH environment variables for third-party DLLs
Any additional help would be appreciated ;-) \ No newline at end of file