Hi everyone.
Did anybody test libSDL 1.2.9 on MacOSX 10.3.9? For I tried it, and I
have much problems…
First, I tried to use the binary framework. When I try to buid the
basic example application that is provided in the developper’s package,
I get the following messages when linking:
_HICopyAccessibilityActionDescription referenced from QuickTime
expected to be defined in Carbon
_HICopyAccessibilityRoleDescription referenced from QuickTime expected
to be defined in Carbon
_LLCStyleInfoCheckForOpenTypeTables referenced from QuickTime expected
to be defined in ApplicationServices
_LLCStyleInfoGetUserRunFeatures referenced from QuickTime expected to
be defined in ApplicationServices
The only way to get rid out of this message is to comment out every
call to the SDL api!
Then, I tried to re-compile the framework from source, using XCode.
Here is the error message I get at link time:
ld: /usr/lib/gcc/darwin/3.3/libstdc++.a(stl-inst.o) illegal reference
to symbol: std::__throw_bad_alloc() defined in indirectly referenced
dynamic library /usr/lib/libstdc++.6.dylib
Finally, I tried to build the Un*x library from the command line. When
building the dynamic library I get the same message as above. Just
building a static library is okay except it causes problem when
building an app the uses it.
Oh, and since Apple provides both gcc 3.1 and gcc 3.3 for my system, I
tried both and both fail.
What could be the problem? I suspect this mess comes from the fact that
both c++ and objC are used in the same library… And concerning my
initial problem in which the QuickTime framework is involved, I suspect
my Carbon framework is too old for some recent QuickTime features…
Maybe it’s time for me to upgrade to 10.4… or drop MacOS X and to
switch to Linux PPC!!!–
Nicolas P?trikowski
Hi everyone.
Did anybody test libSDL 1.2.9 on MacOSX 10.3.9? For I tried it, and I
have much problems…
First, I tried to use the binary framework. When I try to buid the
basic example application that is provided in the developper’s package,
I get the following messages when linking:
_HICopyAccessibilityActionDescription referenced from QuickTime
expected to be defined in Carbon
_HICopyAccessibilityRoleDescription referenced from QuickTime expected
to be defined in Carbon
_LLCStyleInfoCheckForOpenTypeTables referenced from QuickTime expected
to be defined in ApplicationServices
_LLCStyleInfoGetUserRunFeatures referenced from QuickTime expected to
be defined in ApplicationServices
The only way to get rid out of this message is to comment out every
call to the SDL api!
Then, I tried to re-compile the framework from source, using XCode.
Here is the error message I get at link time:
ld: /usr/lib/gcc/darwin/3.3/libstdc++.a(stl-inst.o) illegal reference
to symbol: std::__throw_bad_alloc() defined in indirectly referenced
dynamic library /usr/lib/libstdc++.6.dylib
Finally, I tried to build the Un*x library from the command line. When
building the dynamic library I get the same message as above. Just
building a static library is okay except it causes problem when
building an app the uses it.
Oh, and since Apple provides both gcc 3.1 and gcc 3.3 for my system, I
tried both and both fail.
What could be the problem? I suspect this mess comes from the fact that
both c++ and objC are used in the same library… And concerning my
initial problem in which the QuickTime framework is involved, I suspect
my Carbon framework is too old for some recent QuickTime features that
libSDL uses… Maybe it’s time for me to upgrade to 10.4… or drop
MacOS X and to switch to Linux PPC!!!–
Nicolas P?trikowski
Did anybody test libSDL 1.2.9 on MacOSX 10.3.9? For I tried it, and I
have much problems…
First, I tried to use the binary framework. When I try to buid the
basic example application that is provided in the developper’s package,
I get the following messages when linking:
_HICopyAccessibilityActionDescription referenced from QuickTime
expected to be defined in Carbon
_HICopyAccessibilityRoleDescription referenced from QuickTime expected
to be defined in Carbon
_LLCStyleInfoCheckForOpenTypeTables referenced from QuickTime expected
to be defined in ApplicationServices
_LLCStyleInfoGetUserRunFeatures referenced from QuickTime expected to
be defined in ApplicationServices
Yep, you can thank Apple for requiring 10.4 APIs in their QuickTime SDK. 
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment
Yep, you can thank Apple for requiring 10.4 APIs in their QuickTime
SDK.
I see…
Is QuickTime required for everything in libSDL, or just for video
related features? In that case if I manage to build from source I
should be able to build a reduced version of the library.
So, do you have an idea about why I get non-QuickTime related messages
when I try to build from source?On 17 apr. 06 Sam Lantinga wrote:
–
Nicolas P?trikowski
So, do you have an idea about why I get non-QuickTime related messages
when I try to build from source?
Make sure you’re building from CVS:
http://www.libsdl.org/cvs.php
See ya!
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment
Did anybody test libSDL 1.2.9 on MacOSX 10.3.9? For I tried it, and I
have much problems…
We’re in the process of trying to fix this issue…I’m of the belief
that if we do some tapdancing with the 10.2.8 SDK, SDL won’t have these
issues with pre-Tiger installations…and build as Universal to boot.
Discussion is here:
http://bugzilla.libsdl.org/show_bug.cgi?id=198
This is discussing the commandline build utils (“the Unix way”) … Eric
Wing has made seperate progress in the XCode project files.
–ryan.
For the record, I have never had any problems building SDL and SDL apps
(using Xcode 1.5) on 10.3.9. I don’t remember what version of QuickTime
I had there, but I think it was 7.x.
I switched to 10.4 and Xcode 2.2 about two months ago, so I can’t
comment about the current state of Xcode 1.5/building-on-10.3 support.
-Christian
For the record, I have never had any problems building SDL and SDL
apps
(using Xcode 1.5) on 10.3.9. I don’t remember what version of
QuickTime
I had there, but I think it was 7.x.
It was specifically the 7.0.4 update for 10.3.9 that causes this
trouble - I spoke to a friend at Apple about it, and he reckoned it
should be possible to work around it by linking against the 10.3.9
SDK Quicktime.framework, instead of the system one. I never got as
far as actually trying that, however (and my friend doesn’t work on
anything remotely related to Quicktime, btw)
H&H
JamesOn 18 Apr 2006, at 09:19, Christian Walther wrote: