Artifactspublic-v0

curl

master
ply4 git calls36 ms289 KiB3 cachedprotocol v2
147 lines5.3 KiBRaw

Building via IDE Project Files

This document describes how to compile, build and install curl and libcurl from sources using legacy versions of Visual Studio 2010 - 2013.

You need to generate the project files before using them. Please run "generate -help" for usage details.

To generate project files for recent versions of Visual Studio instead, use cmake. Refer to INSTALL-CMAKE.md in the docs directory.

Directory Structure

The following directory structure is used for the legacy project files:

somedirectory\
 |_curl
   |_projects
     |_<platform>
       |_<ide>
         |_lib
         |_src

This structure allows for side-by-side compilation of curl on the same machine using different versions of a given compiler (for example VC10 and VC12) and allows for your own application or product to be compiled against those variants of libcurl for example.

Note: Typically this side-by-side compilation is generally only required when 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 and libssh2. If you wish to support these, you 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 of curl and libcurl as well as these dependencies.

somedirectory\
 |_curl
 | |_ build
 |    |_<architecture>
 |      |_<ide>
 |        |_<configuration>
 |          |_lib
 |          |_src
 |
 |_openssl
 | |_ build
 |    |_<architecture>
 |      |_VC <version>
 |        |_<configuration>
 |
 |_libssh2
   |_ build
      |_<architecture>
        |_VC <version>
          |_<configuration>

As OpenSSL does not 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++

To build with VC++, you have to first install VC++ which is part of Visual Studio.

Once you have VC++ installed you should launch the application and open one of the solution or workspace files. The VC directory names are based on the version of Visual C++ that you use. Each version of Visual Studio has a default version of Visual C++. We offer these versions:

  • VC10 (Visual Studio 2010 Version 10.0)
  • VC11 (Visual Studio 2012 Version 11.0)
  • VC12 (Visual Studio 2013 Version 12.0)

Separate solutions are provided for both libcurl and the curl command line tool as well as a solution that includes both projects. libcurl.sln, curl.sln and curl-all.sln, respectively. We recommend using curl-all.sln to build both projects.

For example, if you are using Visual Studio 2010 then you should be able to 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 or libssh2) then you need to add the search path of these DLLs to the configuration's PATH environment. To do that:

  1. Open the 'curl-all.sln' or 'curl.sln' solutions
  2. Right-click on the 'curl' project and select Properties
  3. Navigate to 'Configuration Properties > Debugging > Environment'
  4. 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

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' need to contain the path to both of these.

Notes

The following keywords have been used in the directory hierarchy:

  • <platform> - The platform (For example: Windows)
  • <ide> - The IDE (For example: VC10)
  • <architecture> - The platform architecture (For example: Win32, Win64)
  • <configuration> - The target configuration (For example: DLL Debug, LIB Release - LIB OpenSSL)

Should you wish to help out with some of the items on the TODO list, or find bugs in the project files that need correcting, and would like to submit updated files back then please note that, whilst the solution files can be edited directly, the templates for the project files (which are stored in the git repository) need to be modified rather than the generated project files that Visual Studio uses.

Legacy Windows and SSL

Some of the project configurations use Schannel (Windows SSPI), the native SSL library in Windows. Schannel in earlier Windows versions may be unable to connect to servers that no longer support the legacy handshakes and algorithms used by those versions. If you are using curl in such Windows versions you should choose another SSL backend such as OpenSSL.

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# Building via IDE Project Files
9This document describes how to compile, build and install curl and libcurl
10from sources using legacy versions of Visual Studio 2010 - 2013.
12You need to generate the project files before using them. Please run "generate
13-help" for usage details.
15To generate project files for recent versions of Visual Studio instead, use
16cmake. Refer to INSTALL-CMAKE.md in the docs directory.
18## Directory Structure
20The following directory structure is used for the legacy project files:
22 somedirectory\
23 |_curl
24 |_projects
25 |_<platform>
26 |_<ide>
27 |_lib
28 |_src
30This structure allows for side-by-side compilation of curl on the same machine
31using different versions of a given compiler (for example VC10 and VC12) and
32allows for your own application or product to be compiled against those
33variants of libcurl for example.
35Note: Typically this side-by-side compilation is generally only required when
36a library is being compiled against dynamic runtime libraries.
38## Dependencies
40The projects files also support build configurations that require third party
41dependencies such as OpenSSL and libssh2. If you wish to support these, you
42also need to download and compile those libraries as well.
44To support compilation of these libraries using different versions of
45compilers, the following directory structure has been used for both the output
46of curl and libcurl as well as these dependencies.
48 somedirectory\
49 |_curl
50 | |_ build
51 | |_<architecture>
52 | |_<ide>
53 | |_<configuration>
54 | |_lib
55 | |_src
56 |
57 |_openssl
58 | |_ build
59 | |_<architecture>
60 | |_VC <version>
61 | |_<configuration>
62 |
63 |_libssh2
64 |_ build
65 |_<architecture>
66 |_VC <version>
67 |_<configuration>
69As OpenSSL does not support side-by-side compilation when using different
70versions of Visual Studio, a helper batch file has been provided to assist
71with this. Please run `build-openssl -help` for usage details.
73## Building with Visual C++
75To build with VC++, you have to first install VC++ which is part of Visual
76Studio.
78Once you have VC++ installed you should launch the application and open one of
79the solution or workspace files. The VC directory names are based on the
80version of Visual C++ that you use. Each version of Visual Studio has a
81default version of Visual C++. We offer these versions:
83- VC10 (Visual Studio 2010 Version 10.0)
84- VC11 (Visual Studio 2012 Version 11.0)
85- VC12 (Visual Studio 2013 Version 12.0)
87Separate solutions are provided for both libcurl and the curl command line
88tool as well as a solution that includes both projects. libcurl.sln, curl.sln
89and curl-all.sln, respectively. We recommend using curl-all.sln to build both
90projects.
92For example, if you are using Visual Studio 2010 then you should be able to
93use `VC10\curl-all.sln` to build curl and libcurl.
95## Running DLL based configurations
97If you are a developer and plan to run the curl tool from Visual Studio with
98any third-party libraries (such as OpenSSL or libssh2) then you need to add
99the search path of these DLLs to the configuration's PATH environment. To do
100that:
1021. Open the 'curl-all.sln' or 'curl.sln' solutions
1032. Right-click on the 'curl' project and select Properties
1043. Navigate to 'Configuration Properties > Debugging > Environment'
1054. Add `PATH='Path to DLL';C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem`
107... where `Path to DLL` is the configuration specific path. For example the
108following configurations in Visual Studio 2010 might be:
110DLL Debug - DLL OpenSSL (Win32):
112 PATH=..\..\..\..\..\openssl\build\Win32\VC10\DLL Debug;C:\Windows\System32;
113 C:\Windows;C:\Windows\System32\Wbem
115DLL Debug - DLL OpenSSL (x64):
117 PATH=..\..\..\..\..\openssl\build\Win64\VC10\DLL Debug;C:\Windows\System32;
118 C:\Windows;C:\Windows\System32\Wbem
120If you are using a configuration that uses multiple third-party library DLLs
121(such as `DLL Debug - DLL OpenSSL - DLL libssh2`) then 'Path to DLL' need to
122contain the path to both of these.
124## Notes
126The following keywords have been used in the directory hierarchy:
128- `<platform>` - The platform (For example: Windows)
129- `<ide>` - The IDE (For example: VC10)
130- `<architecture>` - The platform architecture (For example: Win32, Win64)
131- `<configuration>` - The target configuration (For example: DLL Debug, LIB
132 Release - LIB OpenSSL)
134Should you wish to help out with some of the items on the TODO list, or find
135bugs in the project files that need correcting, and would like to submit
136updated files back then please note that, whilst the solution files can be
137edited directly, the templates for the project files (which are stored in the
138git repository) need to be modified rather than the generated project files
139that Visual Studio uses.
141## Legacy Windows and SSL
143Some of the project configurations use Schannel (Windows SSPI), the native SSL
144library in Windows. Schannel in earlier Windows versions may be unable to
145connect to servers that no longer support the legacy handshakes and algorithms
146used by those versions. If you are using curl in such Windows versions you
147should choose another SSL backend such as OpenSSL.
Diagnostics4 git calls · 36 ms
CallStatusSizeTime036 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2002.2 KiB · hit31 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=31
git.response.bytes=2245
git.response.cache=HIT
git.response.duration_ms=31
git.fetch.wants=cea21f9e74bf75cedeb49f2efe504784e3f5776c
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=2245
git.pkt.payload.max=2224
git.sideband.band1.bytes=2223
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e2d2015de1cf3a
Request
6009eecf…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format