Fwd: OS back-compatibility
Fwd: OS back-compatibility
- Subject: Fwd: OS back-compatibility
- From: Jonathan Taylor <email@hidden>
- Date: Sun, 23 Apr 2006 19:34:32 +0100
I posted this to the Carbon Dev list by mistake...
For a long time I've avoided the problem of OS back-compatibility by
releasing a CFM-only version of my program. I'd like to include both
a CFM and a Mach-o binary in the package for full compatibility, but
I am having limited success
I'm developing under Tiger, and I've set the target SDK version to
10.1.5 and deployment target to 10.1. When I do this, I get the
following link errors:
/usr/bin/ld: warning can't open dynamic library: /Developer/SDKs/
MacOSX10.1.5.sdk/usr/lib/system/libmathCommon.A.dylib referenced
from: /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../
libSystem.dylib (checking for undefined symbols may be affected) (No
such file or directory, errno = 2)
/usr/bin/ld: Undefined symbols:
_errors referenced from CarbonCore expected to be defined in libSystem
_nan referenced from libSystem expected to be defined in /usr/lib/
system/libmathCommon.A.dylib
_feraiseexcept referenced from libSystem expected to be defined in /
usr/lib/system/libmathCommon.A.dylib
_nanf referenced from libSystem expected to be defined in /usr/lib/
system/libmathCommon.A.dylib
_remquo referenced from libSystem expected to be defined in /usr/lib/
system/libmathCommon.A.dylib
collect2: ld returned 1 exit status
I can't find anything in the archives referring to this problem. Can
anyone suggest what I'm doing wrong? libmathCommon.A.dylib is indeed
not present in the directory it's looking in: there seems to be no
such file in the 10.1.5 SDK tree, and it doesn't exist on a 10.1
system I looked on. Unfortunately I haven't the faintest idea what
I've done wrong to cause those errors: they happen with the built-in
Carbon Application project template if I set target SDK and
deployment target to 10.1.5.
If there is no easy solution to this, I'm quite happy to bundle
together a CFM Carbon and a 10.2.8 Mach-o binary. However... I can't
seem to get that to work as I want either. I have manually added a
CFM Carbon version of the app in Contents/MacOSClassic, and included
an alias to that at the top level of the package. This works as
expected on OS9: the CFM Carbon version is launched successfully.
However on 10.1.5 I had hoped that the CFM version would be launched
when the mach-o version failed to launch... but that doesn't seem to
happen. Is there any way of doing that sort of thing?
Thanks for any pointers for either of these problems
Cheers
Jonny
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden