<div dir="ltr">On Tue, Sep 16, 2008 at 7:49 AM, Ben Sizer <span dir="ltr"><<a href="mailto:kylotan@gmail.com">kylotan@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/9/16 Richard Tew <<a href="mailto:richard.m.tew@gmail.com">richard.m.tew@gmail.com</a>>:<br>
<div class="Ih2E3d">> On Tue, Sep 16, 2008 at 5:39 AM, Ben Sizer <<a href="mailto:kylotan@gmail.com">kylotan@gmail.com</a>> wrote:<br>
>><br>
</div><div class="Ih2E3d">>> I will continue with that for now, but it would be good to get it<br>
>> working with MinGW because a lot of hobbyist game devs use it.<br>
><br>
</div><div class="Ih2E3d">> It works with MinGW. I've used it to compile a Windows native version.<br>
> I've used it to cross-compile a version of Stackless for the Nintendo DS.<br>
><br>
> I believe the problem here is that, as you have stated, you are using a<br>
> custom tool which you are reticent to tinker with its custom MinGW<br>
> environment.<br>
<br>
</div>This isn't a demand to support those environments, by the way. I think<br>
just a little warning on the download/installation page would help, to<br>
avoid confusion. I'd be willing to dig further into it to try and work<br>
out how to fix it myself, if I had a hint on which configuration<br>
option it appears to be tripping up on.<br>
<br></blockquote></div><br>You're right. The binary archive is not suitable for compilation against at this time. I'll see if I can find the time to package up all the include files which come with Stackless, with it.<br>
<br>I should really do a release candidate build for Stackless anyway, given that a corresponding release has been done for Python.<br><br>Cheers,<br>Richard.<br></div>