[openssl-users] Windows Compile Fails

Michael Wojcik Michael.Wojcik at microfocus.com
Fri Jun 19 21:37:30 UTC 2015

> From: openssl-users [mailto:openssl-users-bounces at openssl.org] On Behalf
> Of Jay Foster
> Sent: Friday, June 19, 2015 17:09
> >
> > I think "no-shared" is the Configure option you need. We actually have a
> > script that changes some of the OpenSSL makefiles after configuring, so our
> > process is a bit different from yours.
> >
> That sounds like what I'm running into.  I rebuilt the OpenSSL libraries
> with the "no-shared" option, but this made no difference. Does that work
> for Windows?

Hmm. I thought it did, but as I said we're using a customized process. We run Configure but then make some changes.

You can check to see whether a LIB file is an import or static library using the "lib" tool that's included with Visual Studio. "lib /list libeay32.lib" will show a bunch of object file names if it's a static library; if it's an import library, it will just print "libeay32.dll" a bunch of times.

The static library will also be a lot bigger. My libeay32.lib is around 14 MB. I don't have an import one here, but it should be much smaller, since it's basically just a list of function signatures.

Is it possible your build created both static and dynamic versions? Do you have two different versions of libeay32.lib in the build directory?

What version of OpenSSL are you building?

Michael Wojcik
Technology Specialist, Micro Focus

More information about the openssl-users mailing list