• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
weak linking woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

weak linking woes


  • Subject: weak linking woes
  • From: John Mikros <email@hidden>
  • Date: Wed, 3 May 2006 21:05:22 -0700

I'm trying to link to a framework that may or may not exist depending on whether QuickTime 7 is installed specifically, QuartzCore.framework.

I was hoping that AvailabilityMacros would be enough for things to just work. It's not; dyld complains that it can't find the library. I found the documentation stating that I need to move QuartzCore.framework out of the "Link Binary With Libraries" build phase and into "Other Linker Flags": OTHER_LDFLAGS = -weak_framework QuartzCore. Great, the app launches on 10.3.9 without QuartzCore installed.

However, when execution reaches the first Cocoa call (specifically, [[NSAutoreleasePool alloc] init]), the app blows up, when running under 10.3.9. If I take out all references to any QuartzCore routines, my Cocoa calls work fine.

Anyone have any ideas what may be going on?

thanks
-john
_______________________________________________
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


  • Follow-Ups:
    • Re: weak linking woes
      • From: John Mikros <email@hidden>
  • Prev by Date: Re: XCode Resource Files
  • Next by Date: Re: problem with operator new
  • Previous by thread: Executable path is nil!
  • Next by thread: Re: weak linking woes
  • Index(es):
    • Date
    • Thread