Replies: 1 comment
-
|
AFAICT a goal of vcpkg is that you use one and only one version of each dependency. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I'm trying to use vcpkg to manage my project's dependencies. From what I have read, if I'm using manifest mode, I have to specify the installed packages' versions in the top level vcpkg.json. This would be problematic, for example, if one of my project's dependencies needed OpenCV 4.4.0, and another dependency needed OpenCV 4.10.0, as I would be unable to specify both in the vcpkg.json.
I'm not sure if this is how vcpkg should behave, as I started using it quite recently, so I would like to know if there is a way to use multiple versions of the same library in the dependency tree. Perhaps this is possible, but only for libraries that provide precompiled binaries, for some reason? Or maybe a dependency's dependencies can be managed in a way that allows this?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions