I see that SDL 0.6e is up, and it seems to fix a bug I ran into the
other day (HW surface bit not cleared). But I can’t grab it from the
page; I get a 404 Not Found. What’s up with that?
Sorry, had some problems with a typo:
rm -r SDL-0.6e
tar zcvf SDL-0.6e.tar.gz SDL-0.6e
Doh!
It’s back up there, try now.
On a sidenote; I’m not interested in rebuilding SDL for Win32, I
would be perfectly happy with the pre-built DLLs you supply. I’ve
had tremendous (sp?) problems with the cross-compiler on your
develop-page when used to build executables for Win32. One of the
problems is that when linking, the compiler needs the cygwin-
library, which is not in the archive…
That’s really odd. Try building the warp example in SDL/examples/warp/
and look at the Makefile to see how the options for the different
platforms work. I haven’t had any trouble at all, as long as I remember
to link -lmingw32 before -lSDL on the link line.
Anyway, I’ll send instructions on using Borland C++ 5.0 with the SDL
DLL files.
I see that SDL 0.6e is up, and it seems to fix a bug I ran into the
other day (HW surface bit not cleared). But I can’t grab it from the
page; I get a 404 Not Found. What’s up with that?
On a sidenote; I’m not interested in rebuilding SDL for Win32, I
would be perfectly happy with the pre-built DLLs you supply. I’ve
had tremendous (sp?) problems with the cross-compiler on your
develop-page when used to build executables for Win32. One of the
problems is that when linking, the compiler needs the cygwin-
library, which is not in the archive…
/Emil
[404]
It’s back up there, try now.
Got it! Thanks.
[Win32 compiling]
That’s really odd. Try building the warp example in SDL/examples/warp/
and look at the Makefile to see how the options for the different
platforms work. I haven’t had any trouble at all, as long as I remember
to link -lmingw32 before -lSDL on the link line.
OK, I’ll try that…
/EmilOn Tue, 14 Apr 1998, Sam Lantinga wrote:
[on Win32 compiling]
That’s really odd. Try building the warp example in SDL/examples/warp/
and look at the Makefile to see how the options for the different
platforms work. I haven’t had any trouble at all, as long as I remember
to link -lmingw32 before -lSDL on the link line.
I did that, and hey! It worked! Now I’ve seen SDL running in Windows!
Much joy. There’s one gripe though; it doesn’t work when I put the
SDL-dx5.dll in the program’s directory – it only works with
SDL-dib.dll… Any theories on why? The computer in question used to
run DX3, but I installed DX5 last weekend. My own (pure DirectX) game
engine runs fine on it. I really want full-screen SDL.
/EmilOn Tue, 14 Apr 1998, Sam Lantinga wrote:
Much joy. There’s one gripe though; it doesn’t work when I put the
SDL-dx5.dll in the program’s directory – it only works with
SDL-dib.dll… Any theories on why? The computer in question used to
run DX3, but I installed DX5 last weekend. My own (pure DirectX) game
engine runs fine on it. I really want full-screen SDL.
DX5 is really annoying about segmentation violations.
The application just goes away and there’s no error message.
stderr is your friend.
It sounds like it detects DX5, but you’re not locking a surface somewhere.
That’s the most likely cause of your problems.
Are you specifying SDL_HWSURFACE in your video mode?