Support OpenSSL 1.1.0 lib names in Windows non-configure builds

[jay]

I did this

winbuild, projects and probably others link to ssleay32.lib and libeay32.lib for OpenSSL. Since the release of OpenSSL 1.1.0 they have changed the library names to libssl.lib and libcrypto.lib.

I expected the following

Even though these build systems aren't dynamically generated I think we will need a way to determine what libs to link to, since any lib that is not found causes an error. I started a thread in openssl-dev about this, but I expect I'll be told to just use the new names.

Related https://curl.haxx.se/mail/lib-2016-08/0104.html cc @rodwiddowson

[gvanem]

BTW if using BoringSSL (as a drop-in replacement for OpenSSL), some of it's functions have been moved to decrepit.lib. AFAICS they are BIO_set_ssl() and BIO_f_ssl(). Which complicates building on Windows even more.

[Mellnik]

Please add support for OpenSSL 1.1.0 Series

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.