Re: Undefined symbols - cross development

Rune,

 

Look in Console.app -- it should tell you why the failure is occurring. I wager that you're not finding the correct libstdc++ library. It will also tell you if there is a different error causing app launch failure.

 

greg norz

---

From: xcode-users-bounces+greg.norz=email@hidden [mailto:xcode-users-bounces+greg.norz=email@hidden] On Behalf Of Rune Lindman
Sent: Tuesday, January 31, 2006 1:58 AM
To: Xcode-Users@Lists. Apple. Com
Subject: Re: Undefined symbols - cross development

As I wrote earlier the app which is quite large runs fine on 10.2.8 when Xcode manages to generate a binary that will start. Problem is that most of the time, the binary generated will not launch but after re-compiling and possibly trying different target settings (but no code changes) the app runs just fine on 10.2.8. I just haven't figured out what causes this. I'm sure that if I only find the reason for the problem the app will continue to run fine on 10.2.8. But as development goes on with the new version we will re-evaluate support for 10.2.8. One reason apart from missing functionality is to be able to build with GCC4 on both ppc and x86. Btw problem is also visible on 10.3.

It seems that something causes Xcode not to weak link frameworks as the app will not even reach main when launched.

Thanks for any pointers.

/Rune

On 31 jan 2006, at 08.46, Chris Espinosa wrote:

On Jan 30, 2006, at 11:00 PM, j o a r wrote:

Shouldn't that be "SDKROOT_ppc = /Developer/SDKs/MacOSX10.2.8.sdk"?

I'm not sure I understood this correctly but as I'm using a lot of functionality from 10.4 and do runtime checks don't I need to use 10.4 SDK? If I use 10.2.8 I get many compile errors.

Giving you errors is the purpose of the SDK. You should use the SDK that represents the baseline OS you're targeting - in your case the 10.2.8 SDK. If you haven't already, you should also read this:

No, that's not true.

You set the Mac OS X Deployment Target to the baseline OS you're targeting.

 He is correctly trying to use 10.4u to exploit APIs available in the latest OS, and it's better to keep with one consistent set of headers and link libraries, and deal with platform issues at runtime via weak linking.

The big problem is that the jump from 10.2.8 to 10.4 may be too big for a reasonably ambitious C++ program to span; only Carbon and parts of Cocoa support SDK development, and other libraries (like OpenGL) need special treatment if you want to deliver a binary that runs from 10.2.8 to 10.4.4. and up.  

So I'd recommend you either give up trying to deploy on 10.2.8-10.4.4 with the option to use Tiger features when available.  Either give up Jaguar compatibility (by setting your Deployment Target to 10.3), or limit yourself to Jaguar features (by using the 10.2.8 SDK).

Chris

 _______________________________________________

Do not post admin requests to the list. They will be ignored.

Xcode-users mailing list      (email@hidden)

Help/Unsubscribe/Update your Subscription:

http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden