I've been using prebuilt dependencies. I couldn't figure out where to
put them in the msys file hierarchy so I customized setup.py. As for
automating the build script to check for MingW I looked into that and
couldn't find any obvious way to do it. I personally have a
distutils.cfg file that tells distutils to build with MingW.
Unfortunately the configuration is not read early enough to be useful.
So it might be better to just document where msys expects all the
various libraries. I may have a try at compiling some of the support
libraries myself. But the last time I tried building SDL 1.2.11 I wasn't
satisfied with the results. It compiled its own version of strdup
instead of using _strdup. It wasn't compatible with the pygame version.
René Dudfield wrote:
Hi,
I noticed you have updated the wiki. Thanks.
http://www.pygame.org/wiki/MingW
Do you usually compile without msys? Or is that when you have
prebuilt dependencies?
I guess we can include that change into the configure scripts. By
making a new detection function which detects normal shell + mingw.
On 7/25/07, Lenard Lindstrom <[EMAIL PROTECTED]> wrote:
In case you are wanting to use the information for the mini sprint today
the other thing I did was to add an msvcr71 equivalent of libmoldname to
the mingw library directory. I downloaded the mingw-runtime-3.11 source,
found the part in the makefile which built libmoldname.a, then modified
it to for msvcr71. It seams to work, but I have not thoroughly tested
it, so am not sure if it works for all the renamed functions. As for the
change to the specs file I mentioned in the other post, this appears to
remove the links to abort and such in msvcrt.dll .
Lenard
Lenard Lindstrom wrote:
> Hi René
>
> I've been thinking about it but have been distracted by other things.
> I will work on it today. Thanks for the reminder.
>
> Lenard
>
>
--
Lenard Lindstrom
<[EMAIL PROTECTED]>
