Issue #15171 has been updated by naruse (Yui NARUSE).


MSP-Greg (Greg L) wrote:
> 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.

It is bad if VC14 build uses OpenSSL libraries built with VC12.
But appveyor build is useful because it runs every commit.

Note that we already have msvc12 CI on rubyci.org.
(but adding msvc14 is difficult with our current budget)

I'm interested in Azure Pipelines but not familiar with it.

----------------------------------------
Feature #15171: OpenSSL 1.1.1 soon available from MSYS2
https://bugs.ruby-lang.org/issues/15171#change-74218

* 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



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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>