So, I've managed to get a .msi of the release candidate, and have successfully installed and run the new version of pike from it. There were/are a few glitches in the process, which I'm going to try to sort through. I suspect they may have something to do with some old libraries and headers I have laying around, or perhaps because I'm using VC9. Even so, I think this qualifies as a major victory for me. I haven't looked through your lengthy notes yet, but I'm sure they'll tell me where I've gone astray.
My goal is to cobble together a service that can be used to compile windows versions of third party modules. That way, a module developer can have some chance of making their module available for windows users.
Bill
On Jul 3, 2012, at 2:36 PM, Martin Stjernholm wrote:
Bill Welliver bill@welliver.org wrote:
Well, mine fails 2 tests in Calendar, but I think it's been doing that for some time:
Yes, I get those too. The fact that they're old doesn't make them any less buggy, imo. A way to help sort it out could be to bisect out the responsible commit.
I also got more errors due to that putenv() seemingly didn't work, but they disappeared now when I started digging. :\ Strange, but I guess they can be written off as observational errors then.
Out of curoisity, what does your windows build environment look like? (OS, compiler, etc)...
sprshd, Windows Vista, Visual Studio 2005, GnuWin32 stuff, and various libraries taken from the net. Everything is quite old by now, but it still works. I wrote a longer explanation how it's set up on the other pike list a while ago. Here's a link in case you missed it: article.gmane.org/gmane.comp.lang.pike.user/8287