Fix versions for dependancies managed by vcpkg to known good values
Opened this issue · 1 comments
sinasojoodi commented
Expected behavior and actual behavior
ANSWER:
The version of dependencies installed by vcpkg has to be fixed to a good value.
Steps to reproduce the problem
ANSWER:
If any new version of a dependency breaks the build, there is currently no way to prevent new installation from picking the latest version of that dependancy
Specifications like the version of the project, operating system, or hardware
ANSWER:
NA
sinasojoodi commented
Currently vcpkg itself is fixed to a version due to a regression introduced a few months back. Need to try and see if the newest and latest version works before incorporating this feature in