Msys and SDL libraries

I’ve been experiencing a problem that I was wondering if anyone else has
experienced…

I can compile and use the main SDL distribution with shared libraries using
mingw and msys using the typical configure, make, make install process.
When I try compiling some of the extra libraries (like SDL_image, SDL_draw,
SDL_ttf) as shared libraries, they usually compile just fine, but trying to
use them (or even running the test apps included in the distributions)
results in an “The application terminated unexpectedly” message.

I’ve tried several things, and it seems that I can can compile the libraries
as static only and they seem to work, and I can also compile them manually
as dll’s and it seems to work fine. Has anyone experienced problems with
dll’s like this??
-------------- next part --------------
A non-text attachment was scrubbed…
Name: winmail.dat
Type: application/ms-tnef
Size: 3468 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20031011/78f95b1c/attachment.bin

Actually I already failed on this. I couldn’t get SDL_gfx compiled with
MinGW. SDL_image compiled with MinGW, but I got a segfault when starting
my program linked against that - as you describe.

I cannot comment if the other MinGW shared libs work as I gave up on
that task after the failure with SDL_gfx and SDL_image, but as
workaround one can compile SDL as shared libraries with Visual C++ and
then “reimp” the SDL_xxx.lib output from MSVC into a libSDL_xxx.a file,
then link your app with MinGW against the latter and drop in the MSVC
DLLs for runtime.

MinGW is a great compiler, but these automake scripts give me much pain
on Windows usually. Often easier to compile with the provided MSVC
projects and then reimport the libs. However, requires the presence of
MSVC, of course…

Peter

PS: What is that “winmail.dat” attachment in your mail?Am So, den 12.10.2003 schrieb Brian Kropf um 04:28:

I’ve been experiencing a problem that I was wondering if anyone else has
experienced…

I can compile and use the main SDL distribution with shared libraries using
mingw and msys using the typical configure, make, make install process.

I think (without being more experienced with autotools) that the problem is
actually in the method that the libtool uses to make the dll’s. I’ll keep
investigating.> ----- Original Message -----

From: sdl-admin@libsdl.org [mailto:sdl-admin at libsdl.org] On Behalf Of Peter
Strempel
Sent: Sunday, October 12, 2003 2:45 AM
To: sdl at libsdl.org
Subject: Re: [SDL] Msys and SDL libraries

Am So, den 12.10.2003 schrieb Brian Kropf um 04:28:

I’ve been experiencing a problem that I was wondering if anyone else has
experienced…

I can compile and use the main SDL distribution with shared libraries
using
mingw and msys using the typical configure, make, make install process.

Actually I already failed on this. I couldn’t get SDL_gfx compiled with
MinGW. SDL_image compiled with MinGW, but I got a segfault when starting
my program linked against that - as you describe.

I cannot comment if the other MinGW shared libs work as I gave up on
that task after the failure with SDL_gfx and SDL_image, but as
workaround one can compile SDL as shared libraries with Visual C++ and
then “reimp” the SDL_xxx.lib output from MSVC into a libSDL_xxx.a file,
then link your app with MinGW against the latter and drop in the MSVC
DLLs for runtime.

MinGW is a great compiler, but these automake scripts give me much pain
on Windows usually. Often easier to compile with the provided MSVC
projects and then reimport the libs. However, requires the presence of
MSVC, of course…

Peter

PS: What is that “winmail.dat” attachment in your mail?


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

I think (without being more experienced with autotools) that the problem is
actually in the method that the libtool uses to make the dll’s. I’ll keep
investigating.

It is. I’ve fixed this in SDL’s CVS, but it breaks on other platforms
(like MacOS X). As soon as all the kinks are worked out, I’ll be migrating
the changes to the other SDL helper libraries I maintain, and announce it on
the SDL mailing list.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment