linker error with Borland about libssh2 HOT 5 CLOSED

This also happens with VS builds. OpenSSL uses Windows APIs defined in crypt32.lib now. What I don't understand is why we are only seeing this with libssh2 1.7.0. Perhaps we only recently started calling an OpenSSL API that had that dependency and the linker doesn't link what it doesn't need so we didn't get an error before.

The obvious quick fix is to always add crypt32.lib to the link libraries when on Windows. I'll make this change to the CMake files.

from libssh2.

Ok. I'll link the crypt32.lib with my project.

from libssh2.

Did you start using a statically compiled OpenSSL? (Or statically linked engines) If you use the DLL version the dependency wouldn't be necessary.

The OpenSSL e_capi.c file is the CAPI engine, which usually links into a separate 'capi.dll' file with a shared library build.

from libssh2.

That's true, crypt32.lib is only needed for statically linked OpenSSL. I've used a static OpenSSL for a while and this issue only appeared recently.

from libssh2.

I've linked the OpenSSL lib staticaly. Thank you for your quick reply. :-)

from libssh2.