[openssl-users] openssl-1.1.0 - Linker error on Windows

[Matt Caswell]

On 25/05/16 14:59, Michael Wojcik wrote:
> [Ugh, HTML email, which Outlook is still incapable of processing
> correctly.]
> 
>> From: openssl-users [mailto:openssl-users-bounces at openssl.org] On
>> Behalf Of Andrew Hartley Sent: Wednesday, May 25, 2016 05:20
> 
>> I’ve built the openssl-1.1.0 library with no-shared config option
>> on Windows.  I’ve linked the library to my application > and fixed
>> the few issues with EVP_MD_CTX deprication.  When I build my
>> application I get the following link errors:
> 
>> 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external
>> symbol __imp__CertFreeCertificateContext at 4 referenced in function
>> _capi_free_key
> 
> You have the CAPI engine linked into libcrypto (rather than
> configuring it for dynamic loading)

IIRC it is no longer possible to build for static linking but
dynamically load engines (there be dragons).

>, so you need to link against the
> Windows CAPI library, which is crypt32.lib. Add /Lcrypt32, either
> when you create libcrypto or when you link your application.
> 

Another possibility, if you are not using the CAPI engine, is to disable
it during the OpenSSL build using the no-capieng Configure option.

Matt