Dr Henson, Thanks so much for your response. Perhaps some clarification is in order. When you state "static libraries" are you referring to libeay32 being statically linked with the c runtime libraries? ...or do you mean my application statically linking in the openssl libraries?
Thanks, Lester -----Original Message----- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. Stephen Henson Sent: Thursday, February 07, 2013 8:00 AM To: openssl-users@openssl.org Subject: Re: fipslink On Wed, Feb 06, 2013, Memmott, Lester wrote: > Jon, > > I???m having trouble with fipslink as well and thought it might help > to compare notes. These are the linker errors I???m getting using > Visual Studio 2008: If you can it is far easier to link against the DLLs created by the FIPS capable OpenSSL. Then you can forget all about fipslink.pl and just link as you normally would. If you have to link against the static libraries then you have to use fipslink.pl to embed the appropriate signature. There are examples in the nt.mak makefile which uses it all the time to created static executables. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
