Confusion over vcpkg manifest mode and binary caching
I have a project which uses exact versioning for several dependencies, and this is all specified in a vcpkg.json
manifest file in the project’s repo.
vcpkg: can I have several versions of the same package installed side-by-side?
I used to use libraw 0.19.0 in my project. Then I started using vcpkg and allowed it to just install the latest libraw package (0.21.2). Then I noticed that the images I was getting from libraw looked kind of different, and wanted to go back to 0.19.0 to see if the libraw version was the culprit. So I added this to my vcpkg.json:
override sub dependencies in vcpkg
I am using vcpkg in manifest mode in CMake, by setting the toolset in the CMakeLists.txt.
I have as a dependency VTK and that has also a Qt dependency, but I am also using Qt in my own project. How can I make so that vcpkg uses the Qt installed in my system instead of compiling it?
What is the difference between cloning a specific tag of vcpkg and the “builtin-baseline” tag in manifest mode
I am a little bit confused about the builtin-baseline tag in vcpkg.