curl/curl
1
1
Fork 0
mirror of https://github.com/curl/curl.git synced 2025-09-11 14:42:40 +03:00
Code Issues Packages Projects Releases Wiki Activity

winbuild/README: document how to clean a build

Browse Source 
- Add a new section explaining that a build can be cleaned by adding the
  keyword "clean" to the build command.

- Add an example of using the "x64 Native Tools" prompt to the VS
  command prompt section.

- Update the Legacy Windows section's lack-of-cipher support warning to
  say "Windows 8 and earlier" instead of "Windows XP and earlier".

Ref: https://github.com/curl/curl/discussions/15277

Closes https://github.com/curl/curl/pull/15291
This commit is contained in:
Jay Satiro 2024-10-14 04:41:33 -04:00
parent 1e01e2b549
commit fde5326293
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
winbuild/README.md
View File

@ -60,7 +60,8 @@ Open a Visual Studio Command prompt:
Using the **'VS [version] [platform] [type] Command Prompt'** menu entry: Using the **'VS [version] [platform] [type] Command Prompt'** menu entry:
where [version] is the Visual Studio version, [platform] is e.g. x64 and where [version] is the Visual Studio version, [platform] is e.g. x64 and
[type] Native of Cross platform build. This type of command prompt may not [type] Native of Cross platform build. This type of command prompt may not
exist in all Visual Studio versions. exist in all Visual Studio versions. For example, to build a 64-bit curl open
the x64 Native Tools prompt.
See also: [Set the Path and Environment Variables for Command-Line Builds](https://docs.microsoft.com/en-us/cpp/build/building-on-the-command-line) See also: [Set the Path and Environment Variables for Command-Line Builds](https://docs.microsoft.com/en-us/cpp/build/building-on-the-command-line)
@ -113,6 +114,17 @@ where `<options>` is one or many of:
- `SSL_PATH=<path>` - Custom path for OpenSSL - `SSL_PATH=<path>` - Custom path for OpenSSL
- `ZLIB_PATH=<path>` - Custom path for zlib - `ZLIB_PATH=<path>` - Custom path for zlib
## Cleaning a build
For most build configurations you can remove a bad build by using the same
options with the added keyword "clean". For example:
nmake /f Makefile.vc mode=static clean
Build errors due to switching Visual Studio platform tools or mistakenly
specifying the wrong machine platform for the tools can usually be solved by
first cleaning the bad build.
## Static linking of Microsoft's C runtime (CRT): ## Static linking of Microsoft's C runtime (CRT):
If you are using mode=static nmake will create and link to the static build If you are using mode=static nmake will create and link to the static build
@ -193,7 +205,7 @@ where `<options>` is one or many of:
When you build curl using the build files in this directory the default SSL When you build curl using the build files in this directory the default SSL
backend will be Schannel (Windows SSPI), the native SSL library that comes backend will be Schannel (Windows SSPI), the native SSL library that comes
with the Windows OS. Schannel in Windows <= XP is not able to connect to with the Windows OS. Schannel in Windows 8 and earlier is not able to connect
servers that no longer support the legacy handshakes and algorithms used by 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 those versions. If you will be using curl in one of those earlier versions of
Windows you should choose another SSL backend like OpenSSL. Windows you should choose another SSL backend like OpenSSL.