As pointed out in #1201 already, the OpenSSL 1.1.x lib names have changed, which as consequence makes impossible to link cURL with OpenSSL > 1.0.2. While the aforementioned PR suggested to make lib names configurable, it were also dicussed to first care about the build process present currently. This PR goes for this, the library names are determined by checking the physical existence of the certain files. The newer OpenSSL libs are preferred, while in general there's no change to the current build approach. The only condition is, that the DEVEL dir has to contain either one or the other set of libs, not both at once.
basic support for OpenSSL 1.1.x on windows
@weltling, thanks for your PR! By analyzing the history of the files in this pull request, we identified @yangtse, @mback2k and @msnelling to be potential reviewers.
crypt32.lib is twice and also why ws2_32, is that needed?
Indeed, my typo. Too much of makefiles today :) I was basically refering to https://github.com/openssl/openssl/blob/master/NOTES.WIN#L114, but i see now the ws2_32 and advapi32 are added with WIN_LIBS, so we should be all fine with accordance to the doc.
don't add libs twice
FWIW, I just pulled this down and did a build - changed my build to not do anything special for OpenSSL and it worked a treat.
winbuild: add basic support for OpenSSL 1.1.x
- Auto-detect OpenSSL 1.1 libs