Visual-studio – Included OpenSSL as a static library, but it’s still looking for a DLL

dllopensslstatic-librariesvisual studio

I installed OpenSSL 1.0.0 on Windows using the installer available at:
http://www.slproweb.com/products/Win32OpenSSL.html

I added the .lib files to my project (this is Visual Studio, added it to Project Settings->Linker->Input), and it compiles and works fine. But when I remove the OpenSSL DLL files in Windows\system32, it complains that

"Debugger:: An unhandled non-continuable STATUS_DLL_NOT_FOUND exception was thrown during process load"

Any idea why it's still looking for the DLL even when it's compiled with the static libs? I'm not referencing the DLLs anywhere in the project. The static libs I included are libeay32.lib and ssleay32.lib.

Thanks,
-M

Best Answer

use libeay32MT.lib file that have almost 19 mb size as your library. because it is a static library but libeay32.lib is a library for using the dll.

Related Solutions

C++ – Can’t add static lib

You're doing everything correctly. "Add Reference" is for .NET assemblies (and COM components used via .NET COM interop). The second approach that you've tried is the correct way to do this for native code, but libeay32.lib is not a static library; it's an export library for the DLL.

C++ – ny way to building static Qt with static OpenSSL

Is there any way to building static Qt with static OpenSSL?

Sure, you need to use the following option when configuring Qt:

-openssl-linked

The reason is that QtNetwork uses the QLibrary class by default for dynamically opening the library to get the necessary symbols.

This is the option to tell Qt not to do so, and respect the the normal linkage rules.

That being said, it is not recommended to use static linkage for openssl if security updates need to be available for the end user without your involvement. Consider that for a moment what happens if you are gone, not working on this project anymore, etc.

Also, this setup is not tested frequently, so you may actually encounter some issues that should be fixed upstream, but this is solution design for the use case in question.

Disclaimer: since SO is about programming, I am ignoring the licensing consequences for static linking againt Qt, so I would just like to quickly remind that you that be aware of the proper usage not to get into legal troubles.

Best Answer

Related Solutions

C++ – Can’t add static lib

C++ – ny way to building static Qt with static OpenSSL

Related Topic