You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello !
I'm trying to understand what I'm doing wrong regarding my usage of find_package for openssl.
I'm fairly new to using vcpkg and I'm trying to understand how the vcpkg find_package works.
I'm on windows with the cmake vcpkg toolchain and the triplet x64-windows (and vcpkg classic mode).
I noticed the OpenSSLConfig.cmake can retrieve the .dll filepath (defined in the target IMPORTED_LOCATION).
I'm using this variable to install the .dll along with other runtimes files.
If I use the find_package config mode, I can effectively retrieve this path by using:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello !
I'm trying to understand what I'm doing wrong regarding my usage of find_package for openssl.
I'm fairly new to using vcpkg and I'm trying to understand how the vcpkg find_package works.
I'm on windows with the cmake vcpkg toolchain and the triplet x64-windows (and vcpkg classic mode).
I noticed the OpenSSLConfig.cmake can retrieve the .dll filepath (defined in the target IMPORTED_LOCATION).
I'm using this variable to install the .dll along with other runtimes files.
If I use the find_package config mode, I can effectively retrieve this path by using:
However, this seems like a hack and I'm not even sure of the implications behind it.
Is there a way to retrieve the .dll location using find_package and vcpkg ?
Thank you for your help
Beta Was this translation helpful? Give feedback.
All reactions