Lines Matching +full:- +full:- +full:add +full:- +full:architecture

1 <!--
4 SPDX-License-Identifier: curl
5 -->
11 from sources using legacy versions of Visual Studio 2010 - 2013.
14 "generate -help" for usage details.
17 cmake. Refer to INSTALL-CMAKE in the docs directory.
31 This structure allows for side-by-side compilation of curl on the same machine
36 Note: Typically this side-by-side compilation is generally only required when
52      |    |_<architecture>
60      |    |_<architecture>
66           |_<architecture>
70 As OpenSSL and wolfSSL don't support side-by-side compilation when using
72 provided to assist with this. Please run `build-openssl -help` and/or
73 `build-wolfssl -help` for usage details.
85  - VC10      (Visual Studio 2010 Version 10.0)
86  - VC11      (Visual Studio 2012 Version 11.0)
87  - VC12      (Visual Studio 2013 Version 12.0)
91 and curl-all.sln, respectively. We recommend using curl-all.sln to build both
95 use `VC10\curl-all.sln` to build curl and libcurl.
100 any third-party libraries (such as OpenSSL, wolfSSL or LibSSH2) then you will
101 need to add the search path of these DLLs to the configuration's PATH
104  1. Open the 'curl-all.sln' or 'curl.sln' solutions
105  2. Right-click on the 'curl' project and select Properties
107  4. Add `PATH='Path to DLL';C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem`
112 DLL Debug - DLL OpenSSL (Win32):
117 DLL Debug - DLL OpenSSL (x64):
122 DLL Debug - DLL wolfSSL (Win32):
127 DLL Debug - DLL wolfSSL (x64):
132 If you are using a configuration that uses multiple third-party library DLLs
133 (such as DLL Debug - DLL OpenSSL - DLL LibSSH2) then 'Path to DLL' will need
140  - `<platform>`      - The platform (For example: Windows)
141  - `<ide>`           - The IDE (For example: VC10)
142  - `<architecture>`  - The platform architecture (For example: Win32, Win64)
143  - `<configuration>` - The target configuration (For example: DLL Debug, LIB
144    Release - LIB OpenSSL)