Our scripts have *never*, as far as I know, produced libraries named
like that. Don't those DLLs come from some specific packager that
produces binary install kits?
For 1.1.x, *our* naming is a bit more elaborate, you will see these
names:
libcrypto-1_1.dll & libssl-1_1.dll - VC-WIN32 build
libcrypto-1_1-x64.dll & libssl-1_1-x64.dll - VC-WIN64A build
libcrypto-1_1-ia64.dll & libssl-1_1-ia64.dll - VC-WIN64I build
You will also see the corresponding import libraries: libcrypto.lib &
libssl.lib
Cheers,
Richard
In message
<byapr17mb2150827bb4432c4b7edaf69ddf...@byapr17mb2150.namprd17.prod.outlook.com>
on Mon, 1 Oct 2018 16:29:15 +0000, <aaron.frie...@non.keysight.com> said:
> A current project using Net-SNMP and OpenSSL require that these both are
> built locally (customer
> requirement).
>
> I am attempting to build OpenSSL 1.1.1.
>
> After building OpenSSL, “nmake test” succeeds.
>
> However, the Net-SNMP build is looking for various .lib files that are in the
> pre-built package, but
> do not seem to be in what I build locally.
>
> From the pre-built package, in the lib/VC folder:
>
> libcrypto64MD.lib
>
> libcrypto64MDd.lib
>
> libcrypto64MT.lib
>
> libcrypto64MTd.lib
>
> libssl64MD.lib
>
> libssl64MDd.lib
>
> libssl64MT.lib
>
> libssl64MTd.lib
>
> But the VC folder is not part of my locally built version.
>
> What am I missing in order to get these .lib files to build locally?
>
> Thank you for your assistance.
>
> Best Regards,
> Aaron Friesen
>
> Contract Software Engineer of Aerotek on behalf of Keysight
>
> Keysight Technologies, Inc.
>
> 970.679.5632 T
>
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
