Hi, Everyone,

There is a small feedback about OpenSSL-1.1.0 builds using MSVC:

• in file \Configurations\10-main.conf compiler options /Ox /O2 /Ob2 could be reduced to /O2, since it include all of them (see /O2 and /Ox),
• there is a message:

It looks like you don't have either nmake.exe or dmake.exe on your PATH,
so you will not be able to execute the commands from a Makefile.  You can
install dmake.exe with the Perl Package Manager by running:

    ppm install dmake

during OpenSSL configuration, regardless, that nmake.exe available in PATH and further build using MSVC run successfully.
But even in opposite case, it's weird. Since nmake.exe exists in the same directory as cl.exe. Thus if nmake not available, it mean that cl not available too and dmake won't help much,

• there is some noise in stderr:

Could Not Find c:\libOPENSSL-1.1.0-dev\src\apps\libcrypto-1_1-x64.dll
Could Not Find c:\libOPENSSL-1.1.0-dev\src\test\libcrypto-1_1-x64.dll
Could Not Find c:\libOPENSSL-1.1.0-dev\src\apps\libssl-1_1-x64.dll
Could Not Find c:\libOPENSSL-1.1.0-dev\src\test\libssl-1_1-x64.dll

in the end of nmake run. Inherent to shared builds only, and have any consequences in practice,

• file apps\openssl.cnf not copied into --openssldir=... specified directory during installation, unlike of Mingw-w64 builds,
• OpenSSL MSVC builds doesn't generate html documentation, unlike of Mingw-w64 builds. Wherein ActivePerl, a recommended PERL package for OpenSSL MSVC builds, contain some "adopted" version of pod2html package,

All above relate to OpenSSL builds using MSVC, thus was reported as a single issue. But let me know, if some of paragraphs worth to be submitted as a separate issue.

Regards,
Alexander