-
|
I had issues with installing specific packages (libsndfile, fftw3) which came down to the fact that the new vcpkg environment applies different scriptnames than the portfiles do (vcpkg_cmake_configure instead of vcpkg_configure_cmake etc.). |
Beta Was this translation helpful? Give feedback.
Answered by
vvoois
May 27, 2025
Replies: 1 comment 1 reply
-
|
IIRC all ports in the curated registry are using new vcpkg-cmake. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I figured out what might have been the reason, though it took a while before i got to it:
I cloned the repository through VS2022 in user mode, yet ran the bootstrap batch file in an elevated console prompt.
Eventually, cleared the complete install and cloned and bootstrapped vcpkg with git in an elevated powershell session -> that worked out