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

docs: use lowercase curl and libcurl

Browse source 
Adjusted badwords to find them.

Plus: make badwords run on all markdown files in the repo and update
markdowns previously unchecked

Closes #15898
This commit is contained in:
Daniel Stenberg 2025-01-02 14:43:23 +01:00
parent e694c8284a
commit 3eb57d6ba7
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
60 changed files with 273 additions and 241 deletions
Download patch file Download diff file Expand all files Collapse all files

38
projects/README.md
View file

@ -10,8 +10,8 @@ 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 will need to generate the project files before using them. Please run
"generate -help" for usage details.
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 in the docs directory.
@ -43,7 +43,7 @@ a library is being compiled against dynamic runtime libraries.
The projects files also support build configurations that require third party
dependencies such as OpenSSL and libssh2. If you wish to support these, you
will also need to download and compile those libraries as well.
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
@ -70,19 +70,19 @@ of curl and libcurl as well as these dependencies.
|_VC <version>
|_<configuration>
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.
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 will of course have to first install VC++ which is
part of Visual Studio.
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 will be using. Each version of Visual Studio
has a default version of Visual C++. We offer these versions:
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)
@ -99,9 +99,9 @@ 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 will
need to add the search path of these DLLs to the configuration's PATH
environment. To do that:
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
@ -122,8 +122,8 @@ DLL Debug - DLL OpenSSL (x64):
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.
(such as DLL Debug - DLL OpenSSL - DLL libssh2) then 'Path to DLL' need to
contain the path to both of these.
## Notes
@ -139,14 +139,14 @@ 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) will need to be modified rather than the generated project
files that Visual Studio uses.
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 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
and algorithms used by those versions. If you are using curl in one of those
earlier versions of Windows you should choose another SSL backend like
OpenSSL.