• 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
Re: Target Dependancy Problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Target Dependancy Problem


  • Subject: Re: Target Dependancy Problem
  • From: Peer Allan <email@hidden>
  • Date: Sun, 15 Jan 2006 09:40:38 -0600

Thanks Chris this solved it.

It behaved exactly as you described when I turned off ZeroLink. Everything else you described was setup correctly also except the except the Frameworks was not showing up in the "Link Binary With Libraries" build phase. I clicked the "Target Membership" column off then on again and the framework showed-up in that phase.

Thanks again.

Peer Allan
------------------------
Vice-President and Co-Founder
Bipolar Software Inc.
40 Saturn Bay, Winnipeg, MB, Canada, R3T 0Z9

Voice Mail: (204) 480-0546
Fax: (204) 480-0564

www.bipolarsoftware.ca


On Jan 14, 2006, at 11:29 PM, Chris Hanson wrote:

On Jan 14, 2006, at 3:01 PM, Peer Allan wrote:

I am developing an application and a framework that it is dependent upon. I have linked the 2 projects together, with target dependencies, and everything appears to be linking and compiling correctly except for one important thing. The classes that are part of the Framework are not working in the application. The header file is being imported. If I instantiate an object from the framework and attempt to view its class ( NSLog(@"%@", [object class]) it always outputs NULL. If I comment out the header import then I get the expected compilation errors for unrecognized classes.

If you turn of ZeroLink, do you get linker errors for unrecognized classes? If so, that would indicate that you've only set up a dependency from your application target to your framework target. You also need to link your application against the framework.


You can do this by making your application's target the active target in its Xcode project. Then highlight the framework project in the Groups & Files tree of your application project. Assuming you're using the Xcode's default layout, in the detail view at the right of your project window you'll see the products built by your framework project; there'll also be a column with a checkbox in it whose header looks like a target. That's the Target Membership column, and it should be checked for your framework if it isn't already.

Once you've done this, your framework should show up under the Link Binary With Libraries build phase for your application.

  -- Chris


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Target Dependancy Problem (From: Peer Allan <email@hidden>)
 >Re: Target Dependancy Problem (From: Chris Hanson <email@hidden>)

  • Prev by Date: Re: Hex Editor
  • Next by Date: Re: CORE DATA: setImage (transient) and setImageData (binary) accessors don't fire.
  • Previous by thread: Re: Target Dependancy Problem
  • Next by thread: How to get initial values into dialog via bindings?
  • Index(es):
    • Date
    • Thread