Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OpenSSL] DLLs are not automatically deployed when using in CMake #7366

Open
PhilLab opened this issue Jul 22, 2019 · 2 comments
Open

[OpenSSL] DLLs are not automatically deployed when using in CMake #7366

PhilLab opened this issue Jul 22, 2019 · 2 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@PhilLab
Copy link
Contributor

PhilLab commented Jul 22, 2019

Host Environment

  • OS: Windows
  • Compiler: MSVC 2019

To Reproduce

TARGET_LINK_LIBRARIES(MyProject
    OpenSSL::SSL
    OpenSSL::Crypto)

does not copy the SSL dlls to my project's build folder. Other ports like OpenCV and boost do copy the dlls.

Expected would be to find libeay32.dll and ssleay32.dll

@PhilLab PhilLab added the category:port-bug The issue is with a library, which is something the port should already support label Jul 22, 2019
@JackBoosY
Copy link
Contributor

Probably because openssl uses FindOpenSSL.cmake provided by cmake, vcpkg does not recognize the openssl libraries that needs to be copied.

@JackBoosY JackBoosY added the category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) label Aug 16, 2019
@Rastaban Rastaban assigned ras0219-msft and unassigned Rastaban Aug 20, 2019
@trollixx
Copy link
Contributor

trollixx commented Jul 4, 2020

Looks like the same issue as #2343 I reported a while back. DLLs are not deployed because of dynamic loading.

@JackBoosY JackBoosY removed the category:vcpkg-bug The issue is with the vcpkg system (including helper scripts in `scripts/cmake/`) label Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

5 participants