Hi,
I am experiencing some serious issues with SDL 2.0.3 on OS X. I can
reproduce the behaviour on two different systems, an iMac running 10.6
and a MacMini running 10.9. On both systems SDL randomly seems to turn
off the monitor and go to energy saver mode for no apparent reason. Has
anybody ever heard of such an issue before? It’s really quite scary…
The only rational explanation I can find for this behaviour is that
my build is somewhat messed up. I had to go to quite some pains because
I want to target 10.6 but I only have the 10.8 & 10.9 SDKs. According to
it is still possible, however, to build for 10.6 using a newer SDK.
And the builds do run on 10.6 so it seems possible after all. However,
this sudden monitor and drive switch off is really scaring the heck
out of me.
Here’s what I told ‘configure’:
./configure CFLAGS="-arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -mmacosx-version-min=10.6" --enable-shared=NO
In addition, the environment variable MACOSX_DEPLOYMENT_TARGET is set to "10.6"
and when I link against -lSDL2 I’m also passing
-Wl,-syslibroot,Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk
to gcc.
Before I investigate deeper here I’d just be interested to know if anybody
has ever heard of this issue before or if there’s something else that I need
to keep in mind when building for Mac OS X using plain makefiles.
README-macosx.txt, unfortunately, is not of much help here because it doesn’t
talk about all these intricacies that one is confronted with when building for
"The World’s Most Advanced OS" (cough, cough) without resorting to Xcode…–
Best regards,
Andreas Falkenhahn mailto:@Andreas_Falkenhahn