In message <39de3d0c-b9f8-6576-b4ed-de4501fcb8d5@xxxxxxxxxx> on Tue, 10 Jan 2017 20:20:30 +0100, Jakob Bohm <jb-openssl@xxxxxxxxxx> said: jb-openssl> On 10/01/2017 19:43, Matt Caswell wrote: jb-openssl> > Notes on Perl on Windows jb-openssl> > ------------------------ jb-openssl> > jb-openssl> > There are a number of build targets that can be viewed as "Windows". jb-openssl> > Indeed, there are VC-* configs targeting VisualStudio C, as well as jb-openssl> > MinGW and Cygwin. The key recommendation is to use "matching" Perl, jb-openssl> > one that matches build environment. For example, if you will build jb-openssl> > on Cygwin be sure to use the Cygwin package manager to install Perl. jb-openssl> > For MSYS builds use the MSYS provided Perl. For VC-* builds we jb-openssl> > recommend ActiveState Perl, available from jb-openssl> > http://www.activestate.com/ActivePerl. jb-openssl> > jb-openssl> Really?, I thought ActiveState ActivePerl was pretty much jb-openssl> dead/historic. Looking at their downloads page, they seem to keep up: http://www.activestate.com/activeperl/downloads jb-openssl> While I have not bothered with OpenSSL 1.1.x builds yet, I usually use jb-openssl> Strawberry Perl for VC-related work, and it seems to work fine with jb-openssl> the jb-openssl> 1.0.2 sources. Since I have not tested with 1.1.x sources, this is jb-openssl> obviously not intended as advice to people trying to build, more as jb-openssl> something you might consider for an updated version of NOTES.PERL jb-openssl> (after testing it of cause). I've heard of more than one success with Strawberry, we just haven't tested it ourselves. Cheers, Richard -- Richard Levitte levitte@xxxxxxxxxxx OpenSSL Project http://www.openssl.org/~levitte/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
