SDK vs Deployment target and linking with standard C++ libraries
SDK vs Deployment target and linking with standard C++ libraries
- Subject: SDK vs Deployment target and linking with standard C++ libraries
- From: John Pattenden <email@hidden>
- Date: Thu, 29 Nov 2007 14:24:47 -0500
This is on Leopard with Xcode 2.5 (3.0 is also installed) and GCC 3.3
I would like to build an app that runs down to 10.2.8 but I also want
to use the 10.3.9 sdk and to weak link in some 10.3 APIs
Here is where I am, if I spec a deployment target of 10.2 and the
10.2.8 sdk and comment out all my 10.3.9 APIS my app will run fine on
10.2.8
But if I switch to the 10.3.9 sdk and keep 10.2 as the deployment
target I get the message
"can't open /usr/lib/libstdc++6.dylib"
Which is understandable since it is not installed on 10.2.8
By my reading of the docs specing 10.2 as the deployment target should
encourage Xcode to link again 10.2 compatible libraries
This scenario was working fine for me on Xcode 2.4.
It would be incredibly helpful if someone could point me in the right
direction here, how do I build with the 10.3.9 sdk but have an app
that will link with 10.2 compatible C libraries?
I have set
GCC_VERSION_ppc = 3.3
SDKROOT_ppc = MacOSX10.3.9.sdk
Mac OS X Deployment Target = Mac OS X 10.2
john pattenden
screentime media
_______________________________________________
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