I did an effort to get a Windows 10 environment up this weekend, but it's not done. So here is a release candidate together with an old classically compiled Windows version. If no one finds anything bad (where bad is worse than the latest stable) this will be the release next weekend.
Pike 8.0.240 beta/release candidate:
https://pike.lysator.liu.se/pub/pike/beta/8.0.240/Pike-v8.0.240.tar.gz
Other builds:
https://pike.lysator.liu.se/pub/pike/beta/8.0.240/Pike-v8.0.240-win32-oldlib...
On Tue, May 10, 2016 at 6:26 AM, Peter Bortas bortas@gmail.com wrote:
I did an effort to get a Windows 10 environment up this weekend, but it's not done. So here is a release candidate together with an old classically compiled Windows version. If no one finds anything bad (where bad is worse than the latest stable) this will be the release next weekend.
Nothing worse than current stable noticed, but it's also still the old GTK libs, so it's exactly the same. +0.
Pike 8.0.240 beta/release candidate:
https://pike.lysator.liu.se/pub/pike/beta/8.0.240/Pike-v8.0.240.tar.gz
Other builds:
https://pike.lysator.liu.se/pub/pike/beta/8.0.240/Pike-v8.0.240-win32-oldlibs.msi
I ran into some SSL certificate issues, actually. On my VMs, there were problems with the signing authority not being recognized, although that's possibly because I didn't bother to run Windows Update on a Win 7 computer that's about to do one job and then be deleted. More notably, the Common Name for the cert is "pike.ida.liu.se". Since I know that that's the previous name for the server, this doesn't bother me - but a new user would rightly be suspicious.
ChrisA
pike-devel@lists.lysator.liu.se