mirror of
https://github.com/curl/curl.git
synced 2026-08-24 11:33:33 +03:00
projects: Update VC version names for VS2017, VS2022
- Rename VC15 -> VC14.10, VC17 -> VC14.30. The projects directory that holds the pre-generated Visual Studio project files uses VC<ver> to indicate the MSVC version. At some point support for Visual Studio 2017 (Visual Studio version 15 which uses MSVC 14.10) was added as VC15. Visual Studio 2022 (Visual Studio version 17 which uses MSVC 14.30) project files were recently added and followed that same format using VC17. There is no such MSVC version (yet) as VC15 or VC17. For VS 2017 for example, the name we use is correct as either VS17, VS2017, VC14.10. I opted for the latter since we use VC for earlier versions (eg VC10, VC12, etc). Ref: https://github.com/curl/curl/pull/8438#issuecomment-1037070192 Closes https://github.com/curl/curl/pull/8447
This commit is contained in:
parent
87da3e845b
commit
f7376547bf
24 changed files with 512 additions and 499 deletions
|
|
@ -76,11 +76,24 @@ Building with Visual C++
|
|||
* Microsoft Visual Studio 2010 or above
|
||||
|
||||
Once you have VC++ installed you should launch the application and open one
|
||||
of the solution or workspace files.
|
||||
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:
|
||||
|
||||
Whilst files are provided for both libcurl and the curl command line tool as
|
||||
well as a configuration that includes both, it is recommend that you use the
|
||||
all-in-one configuration.
|
||||
- VC10 (Visual Studio 2010 Version 10.0)
|
||||
- VC11 (Visual Studio 2012 Version 11.0)
|
||||
- VC12 (Visual Studio 2013 Version 12.0)
|
||||
- VC14 (Visual Studio 2015 Version 14.0)
|
||||
- VC14.10 (Visual Studio 2017 Version 15.0)
|
||||
- VC14.30 (Visual Studio 2022 Version 17.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 2022 then you should be able to
|
||||
use VC14.30\curl-all.sln to build curl and libcurl.
|
||||
|
||||
Running DLL based configurations
|
||||
================================
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue