The SDL forums have moved to discourse.libsdl.org.
This is just a read-only archive of the previous forums, to keep old links working.

Hello everyone, since I can't compile SDL on my Windows system, could someone link a pre-compiled SDL 1.3 development library for MinGW, please?
That would be very nice, since I've been looking for it for months, with no success...
So, thanks in advance!

P.S. I think I already have the .dll file, so don't bother linking that!

Seriously guys, what do I need to do to get a working devel. library for MinGW?
Please, someone either tell me exactly how to build that stuff on Windows, or just upload the library somewhere.
It seems the hardest thing in the world, I'm almost going to shoot myself.
I'm spending days and days just to figure out how to compile a library, while I'm sure most of you could do it for me in no time...

On Mon, Sep 28, 2009 at 10:51, MindFlyer wrote:

Uh... the download page??
http://www.libsdl.org/download-1.2.php
I see a dev package for mingw32 right there.
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Hello !




Please have a look at the subject, he is looking
for SDL 1.3 development libs, not 1.2.


CU

_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

2009/9/28 MindFlyer


see here for mingw compatible directx sdk:
http://alleg.sourceforge.net/wip.html 


If you can't figure it out from there, give up.

2009/9/28 Kenneth Bull


also here:
http://sourceforge.net/projects/mingwdx/

Yes ok, thanks. But that doesn't look like the devel. library for SDL 1.3. How is that going to help me?
Actually, it's just a bunch of MORE source code. See, the problem is that I can't compile stuff in Windows, because Windows sucks. You wanted to hear that, so I say it. No need to hate me or to tell me to give up just because I use Windows, thanks.

2009/9/28 MindFlyer:

mingwdx has makefiles and a build tool. You build the library first.
For the other one, dx80_mgw.zip contains the include files and static
libraries needed.
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

2009/9/28 Kenneth Bull:

use them to build SDL yourself. Any DLL you get from someone else
right now will be out of date within a few hours, so don't bother.
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

On Mon, Sep 28, 2009 at 11:43, Torsten Giebl wrote:

Crap, yeah, didn't see that, nevermind.
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Ok, so let's put it this way: I can't possibly compile SDL and all that stuff on Windows, because I'm too dumb to get makefiles to work, and there's no possible way for me to deal with them. But I'm perfectly fine with SDL and programming in general, as long as I have the precompiled library. So I won't give up, if the problem is only getting a bloody library file...

Also, I don't care if my SDL is outdated, because I just need a version without the nasty mouse bug that 1.2.13 has.

So, let's modify my initial question: could someone provide the MinGW devel. libraries for SDL 1.2.14?
The source is here: http://www.libsdl.org/tmp/SDL-1.2.zip

Thanks in advance.

If you're still interested in 1.3 try this build of rev 4853
http://www.mediafire.com/download.php?glynkgmz3rx
It just wouldn't compile with Dev-C++ (probably my fault and I think I know where I started off wrong), but it uses the same type of libraries as VS.

Thanks a lot for your kindness!!!
I try compiling my program with that, but i get this:



Any idea of what it could be?
I also noticed the .a files you sent me are considerably smaller than the 1.2 ones that I had... Weird.

Hmm, it looks like it wants the msvcrt runtime library badly. I tried it on my own project and it compiles, but crashes before it's even initialized. though it was originally made for 1.2 and I have only replaced the includes and libraries with no modifications.

Ok, take 2! This time compiled with wxDev-C++ (extended version of Dev-C++ with some design options) instead of Visual Studio. Finally fixed the compiling problems (extra header file, libraries having to be pointed out specifically instead of just the folder and some stuff was defined twice with no checks for redefinition in the standard DX SDK o_0)
Also it's revision 4878 now.

http://www.mediafire.com/download.php?qynmnjdtvby

I have not tried the Dev-C++ version on my own project. I have other stuff to finalize.

Thank you so much!!!
Now I'm having some trouble converting my SDL 1.2 code to SDL 1.3 code, but it might work...

Ok, my project compiles and I get the executable, but on execution it says that it can't find the procedure SDL_RWFromFP inside SDL.dll.
Any clue of what's going on?

It seems that function is not exported by default. I had to take away the comment on line 82 of SDL_config_win32.h
http://www.mediafire.com/download.php?n3uo2ztnnhn
Keep in mind that it's a development build, so it should have some big bugs.

Thank you so much, man!!! It works now.

Just, the funny thing is that I get the exact same mouse bug that I had on 1.2.13. LOL!
Maybe on 1.3 I have to use some different functions for input and/or mouse handling? It seems that SDL_PollEvent() makes SDL_GetTicks() behave in a very weird way (almost random!) as soon as I move the mouse. Exactly as it did on 1.2.13.

Any clues of what it could be, or any clues on how I can avoid it with the new API?

Thanks again.

Funny thing that I am able to compile SDL 1.3 on Mac with win32 MinGW
cross-compiler without any hassle. So I bet if you have proper MinGW
+MSYS setup on window that shouldn't be a problem for you either. Just
get to MSYS's shell (bash) run "./configure --
prefix=where_to_put_the_compiled_SDL" and then "make" and finally
"make install" to install binary build to
where_to_put_the_compiled_SDL (probably you shall point there your
MinGW folder where you got "include" and "lib".

Unfortunately no clue how to build with Visual Studio (even I got the
license :>)

Regards,
--
Adam Strzelecki | nanoant.com
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

On 09-10-02 7:04 AM, Adam Strzelecki wrote:
You know, Eclipse has a pretty decent C/C++ development environment; I
bet it wouldn't be hard to get it set up building Windows binaries for
SDL apps. Dunno about Mac OS X cross-compiling, I don't remember it
supporting Objective-C at all...

--
Chris Herborth -- http://www.pobox.com/~chrish/
Marooned, the survival game! -- http://marooned-game.livejournal.com/
Never send a monster to do the work of an evil scientist.


_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

I meant opposite direction My target platform was win32 and I did
the compilation on Mac with MinGW win32 cross compiler for Mac. So Obj-
C wasn't an issue.
So SDL-1.3 should compile as well natively with MinGW running on
Windows as I compile it with cross compiler on Mac.

Cheers,
--
Adam Strzelecki | nanoant.com
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Ok, too bad it doesn't.

Anyway, since I already got some working binaries thanks to katz, does anyone have an idea on how I could fix that mouse bug I described above?
Thanks.

Ironically it actually builds faster when cross-compiling from the
Mac, because the UNIX build tools are faster running on the Mach
kernel than the NT kernel.

On Fri, Oct 2, 2009 at 5:34 AM, Adam Strzelecki wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

I put together a snapshot of SDL, SDL_image, SDL_mixer, and SDL_ttf all built for SDL 1.3 with support DLLs and some test programs, along with the relevant mingw32 headers and libraries:
http://www.libsdl.org/tmp/SDL-1.3-mingw32.zip

These were all built cross-compiled from Mac OS X, and tested with Windows 7.

See ya!

On Mon, Sep 28, 2009 at 7:51 AM, MindFlyer wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

OMG, Sam Lantinga!! You're the best, really. Thanks a lot for your kindness!!!

Ok, wait a second.

Among the lib files I see these:
libSDL.a,
libSDL.dll.a,
libSDLmain.a,
libSDL.la.

What do I need to do, link the first 3 files to my project? And in which order?
Because with SDL 1.2 I had only 2, namely libSDL.dll.a and libSDLmain.a.
And what about libSDL.la, what's its purpose? Do I need to link that one, too?

Also, libSDL_image.dll.a, libSDL_mixer.dll.a and libSDL_ttf.dll.a appeared. Do I need to link them all, along with the regular libSDL_image.a, etc? And in which order?

Thank you.

Hello !



libSDL.a is when you want to link with SDL statically,
so you don't need an external SDL.dll then.


libSDL.dll.a is when you want to link with SDL dynamically,
so you need the external SDL.dll then.


libSDLmain.a is the static lib, that contains the clever or nasty
main macro trick.


Is a textfile that contains information about what the name
of the static and dynamic lib is and the paths where libtool has to search
for them.


No.

You need to the same things that sdl-config --libs would link to
and in the same way :

First libSDLmain.a and then libSDL.dll.a

I am curious why there is still a libSDLmain.a there,
was not written everywhere that libSDLmain.a would be absolete
with SDL 1.3 ?


CU

_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Those are a side effect of the mingw32 libtool build process.

Here's the output of sdl-config --libs:
-lmingw32 -lSDLmain -lSDL -mwindows

... which will link with libSDL.a (which I've modified to link to the DLL instead of statically) and libSDLmain.a

See ya!

On Sun, Oct 4, 2009 at 8:10 AM, MindFlyer wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

Ok, here are my comments:

1) At compile time I get this error: `SDL_GL_SWAP_CONTROL' was not declared in this scope.
So how do I force vsynch on and off in 1.3 without SDL_GL_SWAP_CONTROL?

2) SDL_GetMouseState() seems to have 3 parameters now. Since I found no documentation, I tried putting random stuff in there, but nothing seems to change. I get mouse support, but BOTH my mouse cursor AND the standard windows cursor are displayed, one on top of the other. Additionally, and most importantly, the nasty mouse bug I already described is NOT fixed. So the whole purpose of using 1.3 instead of 1.2 has vanished for me...

3) Keyboard support is completely missing, except for the Escape key, which still works.

4) Fonts look very messed up. I use sdl_ttf, print chars on surfaces and convert them to textures with glTexImage2D(). The characters are printed correctly, but on top of them there are lots of parallel lines, or dots, or random crap. The same code used to work perfectly on 1.2. Here's a screenshot:



5) I can't take screenshots with PrintScreen while in fullscreen mode, but that was the case also with 1.2, and I don't know why... -.-

Any idea on how I could fix one or more of these problems? Else I'm switching back to 1.2 and live with that very poor mouse support...

These are all known issues with SDL 1.3.

Can you please enter any bugs in http://bugzilla.libsdl.org ?

Thanks!

On Sun, Oct 4, 2009 at 11:10 AM, MindFlyer wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

I put together an SDL 1.2 version of this snapshot:
http://www.libsdl.org/tmp/SDL-1.2-mingw32.zip

See ya!

On Sun, Oct 4, 2009 at 2:47 AM, Sam Lantinga wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

Sorry?
They are known bugs, but I have to enter them? I don't understand.

Also:

with that 1.2 you just uploaded, I need to include the mikmod.dll file in order to play mp3 files with SDL_mixer. This didn't happen with the old version, and I think it can be avoided... I'm not actually using any of the mikmod functions, I think. So why do I have to carry it around?
Also, I hear a loud CLICK! as soon as the audio starts, which didn't happen in the old version (EDIT: this happens only on Windows Vista), if I remember right. Just like the audio buffer is full of random data the 1st time it plays it... I don't know.

And... Needless to say, the mouse bug is still there.

What is the error? Are you sure you've completely rebuilt with SDL 1.2?

I did test that archive with the included playmus.exe. Does that
work, if you drag an MP3 or Ogg file onto it?

On Sun, Oct 4, 2009 at 4:05 PM, MindFlyer wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

What error? I described a crapload of errors, lol!


Yes. I've substituted all dll files, all lib files, all include files, and I've completely rebuilt my project.


Of course it works, and in the predictable way:
since mikmod.dll is in the directory, he doesn't complain. Also, the CLICK! is still there, but not as loud as in my project. Weird...
My complaint was just that SDL_mixer needed mikmod.dll even if I didn't actually use it inside my project. Which shouldn't happen, and didn't happen with the old SDL_mixer.

What is the return value for Mix_GetError() after the open fails?

SDL_mixer.dll doesn't need mikmod.dll, you only need it if you're using MOD support.

See ya!

On Sun, Oct 4, 2009 at 6:16 PM, MindFlyer wrote:



--
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC

Exactly, BUT Mix_GetError() says that he couldn't find mikmod.dll.