Hi Mr.Henson,
Thankyou so much.
But when nmake -f ms\nt.mak command was given below static libs where
successfully generated.
m. Compiled FIPS compliant OpenSSL fipslibeay32.lib, ssleay32.lib &
libeaycompat32.lib are located at C:\openssl-1.0.2c-fips-compliant\out32
But when nmake -f ms\ntdll.mak command was given fipslibeay32.dll was missing
in the location. But ssleay32.dll was successfully generated.
n. Compiled FIPS compliant OpenSSL fipslibeay32.dll & ssleay32.dll are
located at C:\openssl-1.0.2c-fips-compliant\out32
Please let me know if I need to make changes in ntdll.mak file to generate the
corresponding fipslibeay32.dll .
As I need to include this dll in my test application to turn on the fips module.
Please guide me as I am new to FIPs module.
Thanks&Regards
Ashwini V Patil
-----Original Message-----
From: Stephen Henson via RT [mailto:r...@openssl.org]
Sent: Monday, August 17, 2015 3:50 PM
To: Patil, Ashwini IN BLR STS
Cc: openssl-dev@openssl.org
Subject: Re: [openssl-dev] [openssl.org #3978] RE: Openssl 1.0.2c include the
FIPS 140-2 Object Module
On Mon, Aug 17, 2015, Patil, Ashwini IN BLR STS via RT wrote:
> Hi Mr. Stephen N. Henson,
>
>
>
> Thankyou so much for the reply.
>
>
>
> We would like to use the option1 mentioned by you. But unfortunately the
> dll's were not generated, only static lib's were generated.
>
> Please guide if we have missed any steps.
>
[snip]
>
> g. nmake -f ms\nt.mak
>
This builds the static libraries. If you do:
nmake -f ms\ntdll.mak
you will get the DLLs.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
