Re: [pygame] MSVCR71.dll

[Rene Dudfield <renesd@xxxxxxxxx>]

Yeah, last I heard it was compiling ok with mingw.

Maintaining a separate python interpreter is quite a lot of work. 
Maybe maintaining one which 'only works with pygame/pyopengl/four
other libraries with py2exe' would be easier than one for all python
people.


On 8/29/05, andrew baker <failrate@xxxxxxxxx> wrote:
> Hmmm, I was just able to build Python 2.4 from source on Windows XP
> with Cygwin and gcc.  I then used a simple script to test that the
> executable would actually function.  Now, it required disabling
> threading for the so-called "band-aid" fix, but still, I don't even
> use threads in my games, and there's apparently a more complete fix
> available.  So, it's apparently feasible to compile Python and maybe
> PyGame and all the others in some other compiler than MSVC71.
> 
> On 8/28/05, Brian Fisher <brian_fisher@xxxxxxx> wrote:
> > ------ Original Message ------
> > From: andrew baker <failrate@xxxxxxxxx>
> > > This is a known issue with all py2exe/pygame2exe distributions with
> > > Python 2.4.  For this reason, I am boycotting 2.4 and dependant
> > > modules until it's made free of this burdensome yoke.
> > >
> > > I hope that didn't sound too melodramatic, but I'm really salty about
> > > how the issue affects distribution.
> > >
> > I agree. I know the whole msvcr71.dll is discussed ad naseum on other forums,
> > but I don't plan on using pygame over python 2.4 for similar reasons. I
> > actually have a licensed copy of .NET 2003, but I don't want to deal with
> > having my EULA right to satisfy the redistribution requirements or to even
> > have to add the file size of the dll.
> >
> >
> >
> 
> 
> --
> Andrew Ulysses Baker
> "failrate"
>