Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?
Already knowing that it wouldn’t compile in 64-bit (QuickDraw being no
longer available and all) I tried forcing it to compile in 32-bit by
adding “-arch i386” to my CFLAGS, but hit errors around CoreAudio
stuff.
This was with both the latest SVN and 1.2.13.–
Oh, just noticed the CoreAudio errors are in SDL 1.3 too.On Sun, Aug 30, 2009 at 17:20, Simon Roby<@Simon_Roby> wrote:
Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?Already knowing that it wouldn’t compile in 64-bit (QuickDraw being no
longer available and all) I tried forcing it to compile in 32-bit by
adding “-arch i386” to my CFLAGS, but hit errors around CoreAudio
stuff.This was with both the latest SVN and 1.2.13.
- SR
Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?Already knowing that it wouldn’t compile in 64-bit (QuickDraw being no
longer available and all) I tried forcing it to compile in 32-bit by
adding “-arch i386” to my CFLAGS, but hit errors around CoreAudio
stuff.This was with both the latest SVN and 1.2.13.
I don’t have 10.6 myself but I am told that this helps:
env CC=’/usr/bin/gcc-4.0’ CFLAGS=’-isysroot /Developer/SDKs/
MacOSX10.5.sdk -arch i386’ LDFLAGS=’-arch i386’ ./configure --prefix=/
sw --without-x
They dropped some headers (Carbon being deprecated or so), and using
the 10.5sdk helps with that. Or so… But once again, I couldn’t try
this myself, lacking 10.6.
Cheers,
MaxAm 30.08.2009 um 23:20 schrieb Simon Roby:
Hi,do you think that it could be possible to update the sdl backend for
macos (like dropping quickdraw and compilation at 64bits) in time for sdl
1.3 release?
Best,
VittorioOn Wed, Sep 2, 2009 at 10:09 PM, Max Horn wrote:
Am 30.08.2009 um 23:20 schrieb Simon Roby:
Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?
Already knowing that it wouldn’t compile in 64-bit (QuickDraw being no
longer available and all) I tried forcing it to compile in 32-bit by
adding “-arch i386” to my CFLAGS, but hit errors around CoreAudio
stuff.This was with both the latest SVN and 1.2.13.
I don’t have 10.6 myself but I am told that this helps:
env CC=’/usr/bin/gcc-4.0’ CFLAGS=’-isysroot /Developer/SDKs/MacOSX10.5.sdk
-arch i386’ LDFLAGS=’-arch i386’ ./configure --prefix=/sw --without-xThey dropped some headers (Carbon being deprecated or so), and using the
10.5sdk helps with that. Or so… But once again, I couldn’t try this
myself, lacking 10.6.Cheers,
Max
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
–
Joan Crawfordhttp://www.brainyquote.com/quotes/authors/j/joan_crawford.html
Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?
I don’t know how much work it would be, but there isn’t much QuickDraw
in there…we’re using Cocoa and Quartz, even in 1.2.
Frankly, I wouldn’t object to this being fixed, even if you don’t care
about 64-bit and Snow Leopard, since 10.5 prints a damned warning to
stderr to whine about QuickDraw every time you start an SDL 1.2 application.
–ryan.
Yes, definitely.On Thu, Sep 3, 2009 at 1:23 PM, Vittorio Giovara <vittorio.giovara at gmail.com wrote:
Hi,do you think that it could be possible to update the sdl backend for
macos (like dropping quickdraw and compilation at 64bits) in time for sdl
1.3 release?Best,
VittorioOn Wed, Sep 2, 2009 at 10:09 PM, Max Horn wrote:
Am 30.08.2009 um 23:20 schrieb Simon Roby:
Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?
Already knowing that it wouldn’t compile in 64-bit (QuickDraw being no
longer available and all) I tried forcing it to compile in 32-bit by
adding “-arch i386” to my CFLAGS, but hit errors around CoreAudio
stuff.This was with both the latest SVN and 1.2.13.
I don’t have 10.6 myself but I am told that this helps:
env CC=’/usr/bin/gcc-4.0’ CFLAGS=’-isysroot /Developer/SDKs/MacOSX10.5.sdk
-arch i386’ LDFLAGS=’-arch i386’ ./configure --prefix=/sw --without-xThey dropped some headers (Carbon being deprecated or so), and using the
10.5sdk helps with that. Or so… But once again, I couldn’t try this
myself, lacking 10.6.Cheers,
Max
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org–
Joan Crawfordhttp://www.brainyquote.com/quotes/authors/j/joan_crawford.html - “I, Joan Crawford, I believe in the dollar. Everything I earn, I spend.”
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
–
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
SDL 1.3 builds and runs on Mac OS X 10.6! 
http://www.libsdl.org/tmp/SDL-1.3.zip
See ya!On Sat, Sep 5, 2009 at 12:41 AM, Sam Lantinga <@slouken> wrote:
Yes, definitely.
On Thu, Sep 3, 2009 at 1:23 PM, Vittorio Giovara < vittorio.giovara at gmail.com> wrote:
Hi,do you think that it could be possible to update the sdl backend for
macos (like dropping quickdraw and compilation at 64bits) in time for sdl
1.3 release?Best,
VittorioOn Wed, Sep 2, 2009 at 10:09 PM, Max Horn wrote:
Am 30.08.2009 um 23:20 schrieb Simon Roby:
Just wanted to know, what is the “official” status regarding SDL 1.2
and Snow Leopard? Is there any support planned for it?
Already knowing that it wouldn’t compile in 64-bit (QuickDraw being no
longer available and all) I tried forcing it to compile in 32-bit by
adding “-arch i386” to my CFLAGS, but hit errors around CoreAudio
stuff.This was with both the latest SVN and 1.2.13.
I don’t have 10.6 myself but I am told that this helps:
env CC=’/usr/bin/gcc-4.0’ CFLAGS=’-isysroot
/Developer/SDKs/MacOSX10.5.sdk -arch i386’ LDFLAGS=’-arch i386’ ./configure
–prefix=/sw --without-xThey dropped some headers (Carbon being deprecated or so), and using the
10.5sdk helps with that. Or so… But once again, I couldn’t try this
myself, lacking 10.6.Cheers,
Max
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org–
Joan Crawfordhttp://www.brainyquote.com/quotes/authors/j/joan_crawford.html - “I, Joan Crawford, I believe in the dollar. Everything I earn, I spend.”
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org–
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
–
-Sam Lantinga, Founder and President, Galaxy Gameworks LLC
I’ve downloaded and compiled the framework successfully. And ive tried
creating a new project with the updated templates but I get this error
when i try to compile the project:
ld: duplicate symbol _main in
/Users/dotoli/Documents/apps/qwerty/build/qwerty.build/Debug/qwerty.build/
Objects-normal/i386/main.o and
/Users/dotoli/Documents/apps/qwerty/build/qwerty.build/Debug/qwerty.build/
Objects-normal/i386/SDLMain.o
collect2: ld returned 1 exit status
Command /Developer/usr/bin/g+±4.2 failed with exit code 1
i’ve tried compiling with gcc 4.0 but i get the same thing as well.
is there something im missing?
hi,
I’m not sure this applies to you… but was your program using SDL 1.2
before? SDL 1.3 and 1.2 are not entirely compatible.
There’s not really any documention on how to port from SDL 1.2 to SDL 1.3 yet.
However someone has started adding some stuff into the SDL documentation wiki.
http://www.libsdl.org/cgi/docwiki.cgi/SDL-1.3
… but the docs aren’t finished yet. But that would be a good place
to list changes required to port code.
cu,On Wed, Sep 9, 2009 at 2:44 PM, Olivier Namet<olivier.namet at gmail.com> wrote:
I’ve downloaded and compiled the framework successfully. And ive tried
creating a new project with the updated templates but I get this error
when i try to compile the project:ld: duplicate symbol _main in
/Users/dotoli/Documents/apps/qwerty/build/qwerty.build/Debug/qwerty.build/
Objects-normal/i386/main.o and
/Users/dotoli/Documents/apps/qwerty/build/qwerty.build/Debug/qwerty.build/
Objects-normal/i386/SDLMain.o
collect2: ld returned 1 exit status
Command /Developer/usr/bin/g+±4.2 failed with exit code 1i’ve tried compiling with gcc 4.0 but i get the same thing as well.
?is there something im missing?
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
I have to admit that initially i tried one of my 1.2 projects but
I have also tried creating a brand new project with the templates
in the 1.3 zip file and i still get an error im afraid.
thank you for the link to the wiki page, will def check it out!
Olivier
SDL 1.3 builds and runs on Mac OS X 10.6!
http://www.libsdl.org/tmp/SDL-1.3.zip
That’s nice, but of course it would be even nicer if so did SDL 1.2,
which many people still have to use. With tricks (forcing it to use
the 1.5 SDK), one can still build it for x86 – but not for 64bit
mode, where e.g. QuickDraw is missing, AFAIK.
There was a patch which replaces the QuickDraw code in SDL 1.2 with
modern CoreGraphics code (should run from 1.4 to 1.6, and also be
faster): http://permalink.gmane.org/gmane.comp.lib.sdl/36747. I
didn’t investigate it closely, to be frank, but something like that
might be highly useful.
There might also be issues with CoreAudio v1 still being used in SDL
1.2 (and maybe 1.3? I haven’t checked either, though); if that’s a
case, it should be simple enough to “fix” that. I’d be happy to make a
patch, if necessary.
Cheers,
MaxAm 05.09.2009 um 12:44 schrieb Sam Lantinga:
Well it’s not like 64-bit is essential. But having it cleanly compile
with the 10.6 32-bit SDK would be nice (IMHO).–
On Fri, Sep 11, 2009 at 02:48, Max Horn wrote:
Am 05.09.2009 um 12:44 schrieb Sam Lantinga:
SDL 1.3 builds and runs on Mac OS X 10.6!
http://www.libsdl.org/tmp/SDL-1.3.zipThat’s nice, but of course it would be even nicer if so did SDL 1.2, which
many people still have to use. With tricks (forcing it to use the 1.5 SDK),
one can still build it for x86 – but not for 64bit mode, where e.g.
QuickDraw is missing, AFAIK.There was a patch which replaces the QuickDraw code in SDL 1.2 with modern
CoreGraphics code (should run from 1.4 to 1.6, and also be faster):
http://permalink.gmane.org/gmane.comp.lib.sdl/36747. I didn’t investigate
it closely, to be frank, but something like that might be highly useful.There might also be issues with CoreAudio v1 still being used in SDL 1.2
(and maybe 1.3? I haven’t checked either, though); if that’s a case, it
should be simple enough to “fix” that. I’d be happy to make a patch, if
necessary.Cheers,
Max
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Well it’s not like 64-bit is essential. But having it cleanly compile
with the 10.6 32-bit SDK would be nice (IMHO).
It’s not essential, but QuickDraw is deprecated even in 10.5. It will
eventually die… Hopefully SDL 10.3 is ready by then, and fully
compatible with all existing SDL 1.2 apps, but it seems best to first
upgrade the existing 1.2.x branch to cooperate nicely with the OS
Bye,
MaxAm 11.09.2009 um 18:33 schrieb Simon Roby:
Well it’s not like 64-bit is essential. But having it cleanly compile
with the 10.6 32-bit SDK would be nice (IMHO).
Every other process on my MacBook Pro is 64-bit, so it’s probably about
to become important.
Also: holy crap, I didn’t know someone already moved SDL 1.2 off QuickDraw!
I’ll look into cleaning that patch up.
–ryan.
Well it’s not like 64-bit is essential. But having it cleanly compile
with the 10.6 32-bit SDK would be nice (IMHO).Every other process on my MacBook Pro is 64-bit, so it’s probably
about to become important.Also: holy crap, I didn’t know someone already moved SDL 1.2 off
QuickDraw!I’ll look into cleaning that patch up.
Ryan,
please also see http://bugzilla.libsdl.org/show_bug.cgi?id=581 which
might save you some work.
Cheers,
MaxAm 11.09.2009 um 23:18 schrieb Ryan C. Gordon:
Ryan,
please also see http://bugzilla.libsdl.org/show_bug.cgi?id=581 which
might save you some work.
Already on it.
I cleaned up the rest of 1.2 to be Snow Leopard and 64-bit compatible
this morning, so this is the last thing left. The latest in Bugzilla
works, but it has some issues still and hasn’t been tested beyond
testsprite (which works fine, fwiw).
–ryan.
Hello from the world of MacPorts users. I just saw Ryan Gordon’s
latest note at http://bugzilla.libsdl.org/show_bug.cgi?id=581, which
I take to mean that this issue may never be fixed. On the MacPorts
side, there are over sixty of us cc’ed on this issue (<http://trac.macports.org/ticket/20235
)… most of us, I think, don’t know how to help fix the problem,
but at least a few of us would be willing to make small donations to
help sponsor a fix. Might that help, or is money not an issue?
Thanks,
Allen McBride
Hello from the world of MacPorts users. I just saw Ryan Gordon’s
latest note at http://bugzilla.libsdl.org/show_bug.cgi?id=581, which
I take to mean that this issue may never be fixed. On the MacPorts
side, there are over sixty of us cc’ed on this issue (<http://trac.macports.org/ticket/20235)… most of us, I think, don’t know how to help fix the problem,
but at least a few of us would be willing to make small donations to
help sponsor a fix. Might that help, or is money not an issue?
That comment was attached to almost 100 bugs in a mass-update of
Bugzilla to prepare for a 1.2.14 release.
In the case of that specific bug: we’re definitely fixing it. High priority.
Sorry for any panic I caused.
–ryan.
Thanks! (And sorry if this breaks the threading again; I’m in digest
mode and I just can’t figure out how to reply correctly. If I write
the list again, I’ll try to switch to non-digest beforehand.)
–Allen> That comment was attached to almost 100 bugs in a mass-update of
Bugzilla to prepare for a 1.2.14 release.
In the case of that specific bug: we’re definitely fixing it. High
priority.Sorry for any panic I caused.
–ryan.
Allen McBride wrote:
Hello from the world of MacPorts users. I just saw Ryan Gordon’s
latest note at http://bugzilla.libsdl.org/show_bug.cgi?id=581, which
I take to mean that this issue may never be fixed. On the MacPorts
This fix just hit subversion, and it’s a serious change to the codebase.
PLEASE test the hell out of this. We’d like to know that making SDL 1.2
compatible with 10.6 wasn’t a big mistake at this late stage of the game.
–ryan.