Replies: 2 comments 2 replies
-
@ocornut, thanks for reporting this issue, this looks not support yet. For this particular case, it looks https://github.com/microsoft/vcpkg/blob/master/scripts/buildsystems/msbuild/vcpkg.props hasn't import. @strega-nil-ms, could you please have a look? |
Beta Was this translation helpful? Give feedback.
0 replies
-
For me this is a bug and it should not be moved to the discussions tab. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I have variety of VS version installed. For this report I'll focus on VS 2015 Update 3 and VS 2019.
When project is setup to use v140 toolchain (VS2015): integration is available in VS2015.
Same project loaded in VS2019: the v140 toolchain is called, but vcpkg integration is not available.
Project needs upgrading to v142 toolchain (VS2019) to have vcpkg integration showing and functional.
This is inconsistent with VS offering access to toolchain selection and makes that toolchain selection basically unusable with vcpkg integration.
Project open in VS2015 IDE:
Same project in VS2019 IDE:
(note that
vcpkg
section is missing)Same project in VS2019 IDE after upgrading to toolchain v142:
Here I am showing
vcpkg
section of project properties, as an indicator that vcpkg integration works (it does work in the cases were the vcpkg section appears in that view, it doesn't work in the cases were the vcpkg section doesn't appears).Environment
Microsoft Visual Studio Community 2015 / Version 14.0.25431.01 Update 3
and
Microsoft Visual Studio Community 2019 / Version 16.9.4 / VisualStudio.16.Release/16.9.4+31205.134
To Reproduce
Steps to reproduce the behavior:
Additional context
This is problematic as it breaks the promise of toolchain selection of VS.
Beta Was this translation helpful? Give feedback.
All reactions