> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Short, Todd via openssl-users
> Sent: Monday, October 08, 2018 09:56
> Looks to be debug (d) and multi-thread (MT?) versions of the libraries; not
> sure what MD stands for.
It's Microsoft's naming convention for
Could that be LibreSSL? (Or some similar wrapper for OpenSSL?)
https://github.com/Ruzzz/LibreSSL
This above repo creates libraries in the named format below; to match how
Microsoft provides multiple versions of libraries.
Looks to be debug (d) and multi-thread (MT?) versions of the libraries;
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 -
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
