[ruby-core:90264] [Ruby trunk Feature#15171] [patch] Use OpenSSL 1.1.1 for Appveyor MinGW build

[Greg.mpls@gmail.com]

Issue #15171 has been updated by MSP-Greg (Greg L).


Sorry for the second message.  I did not mention one thing that non Windows users may not be aware of.

Publicly facing Windows Ruby MinGW builds are all self contained.  For instance, I locally test on Rubies from 2.2 thru trunk.  Those five builds use four different sets of OpenSSL dll's.  All that is required to change versions is a change to `ENV['PATH']`.

JFYI, due to that, building/compiling extension gems can be non-trivial.

----------------------------------------
Feature #15171: [patch] Use OpenSSL 1.1.1 for Appveyor MinGW build
https://bugs.ruby-lang.org/issues/15171#change-75379

* Author: MSP-Greg (Greg L)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
@nobu

Thanks for your work with the Appveyor testing.  It took three revisions, but MSYS2 has jumped from OpenSSL 1.0.2 to 1.1.1.  The package release 1.1.1-4 should build fine on Appveyor MinGW.  I don't think it has hit the MSYS2 repository yet, but certainly in the next 24 hours.

If you've got MSYS2 installed, `pacman -Ss mingw-w64-x86_64-openssl` should show availability.  But you knew that.

Hence, line 122 of the current Appveyor.yml file would need mingw-w64-x86_64-openssl added to it.  At present, Appveyor has got 1.0.2p.

Lastly, given any thought to moving the VC builds to Azure?  I may see if I can make both VC12 and VC14 OpenSSL packages.  Seems inappropriate to load different runtimes with (I think) VC12.

Greg

---Files--------------------------------
av_openssl_1.1.1.patch (2.09 KB)


-- 
https://bugs.ruby-lang.org/