Skip to content

Unsupport VS2015 more. #576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BillyONeal wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Unsupport VS2015 more. #576

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion vcpkg/about/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -209,7 +209,7 @@ We recommend building your libraries once with your preferred build configuratio

## What MSVC toolsets are supported?

We support Visual Studio 2015 Update 3 and above.
We support Visual Studio 2017 and above.

## Why does Visual Studio not use my libraries with user-wide integration enabled?

Expand Down
2 changes: 0 additions & 2 deletions vcpkg/commands/integrate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,6 @@ Integrate vcpkg with shells and buildsystems.

Integrates with [Visual Studio](../users/buildsystems/msbuild-integration.md#user-wide-integration) (Windows-only), sets the user-wide vcpkg instance, and displays CMake integration help.

On Windows with Visual Studio 2015, this subcommand will add redirecting logic into the MSBuild installation which will automatically pick up each user's user-wide vcpkg instance. Visual Studio 2017 and newer have this logic in the box.

To set the user-wide vcpkg instance, vcpkg creates a few short files containing the absolute path to the vcpkg instance inside the user's user-wide configuration location:

- `%LOCALAPPDATA%\vcpkg` or `%APPDATA%\Local\vcpkg` on Windows
Expand Down
2 changes: 1 addition & 1 deletion vcpkg/consume/classic-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ to remove MSBuild system-wide integration.
This integration method automatically adds vcpkg-installed packages to the following project properties:
`Include Directories`, `Link Directories`, and `Link Libraries`. Additionally, this creates a post-build action
that ensures that any required DLLs are copied into the build output folder. This works for all solutions and
projects using Visual Studio 2015 or newer.
projects using Visual Studio 2017 or newer.

### [CMake](#tab/cmake)

Expand Down
2 changes: 1 addition & 1 deletion vcpkg/consume/manifest-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ to remove MSBuild system-wide integration.
This integration method automatically adds vcpkg-installed packages to the following project properties:
`Include Directories`, `Link Directories`, and `Link Libraries`. Additionally, this creates a post-build action
that ensures that any required DLLs are copied into the build output folder. This works for all solutions and
projects using Visual Studio 2015 or newer.
projects using Visual Studio 2017 or newer.

### [CMake](#tab/cmake)

Expand Down
2 changes: 1 addition & 1 deletion vcpkg/users/buildsystems/msbuild-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ integration.
This integration method automatically adds vcpkg-installed packages to the following project
properties: Include Directories, Link Directories, and Link Libraries. Additionally, this creates a
post-build action that ensures that any required DLLs are copied into the build output folder. This
works for all solutions and projects using Visual Studio 2015 or newer.
works for all solutions and projects using Visual Studio 2017 or newer.

This is all you need to do for the vast majority of libraries. However, some libraries perform
conflicting behaviors, such as redefining `main()`. Since you need to choose per-project which of
Expand Down
2 changes: 1 addition & 1 deletion vcpkg/users/triplets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -303,10 +303,10 @@ selection algorithm.

Valid settings:

- The Visual Studio 2026 platform toolset is `v145`.
Copy link
Copy Markdown
Collaborator Author

@BillyONeal BillyONeal May 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image

- The Visual Studio 2022 platform toolset is `v143`.
- The Visual Studio 2019 platform toolset is `v142`.
- The Visual Studio 2017 platform toolset is `v141`.
- The Visual Studio 2015 platform toolset is `v140`.

### VCPKG_PLATFORM_TOOLSET_VERSION

Expand Down