• 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: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved


  • Subject: Re: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved
  • From: Chris Hanson <email@hidden>
  • Date: Mon, 10 Dec 2007 17:21:40 -0800

On Dec 10, 2007, at 1:16 PM, Jerry Krinock wrote:

I thought that the purpose of having a framework "in" the project but ^not^ in the target (box not checked) means that it might be used "in" some other target in the project. But now I wonder, is there some effect if a framework is simply "in" the project?

No. I think the effect you're seeing is a result of linking against Cocoa.framework and using symbols from CoreData.framework, not of having CoreData.framework as a project member that isn't used in any target. If you use a symbol like NSPersistentStoreCoordinator that's defined in CoreData.framework, you're going to wind up linking against it.


Why does Apple add these un-linked frameworks to the New Cocoa Application, particularly since they are already linked by the Cocoa.framework "umbrella"?

These non-linked frameworks -- which are conceptually (but not physically, unlike Carbon) part of the Cocoa umbrella -- are added to the project to make it easy to read the headers within the framework.


For example, if you are using the Default or All-in-One layout, you can highlight CoreData.framework in the Groups & Files tree and then see the headers within it in the detail pane to the right. This makes for quick access if you want to find a particular header, especially if you can't quite remember the name. It also means you can use the search field at the top of the window to filter the detail view.

That's all it really does. It's a UI convenience, it doesn't have significant deeper meaning for Xcode.

  -- Chris

_______________________________________________
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: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved
      • From: Jerry Krinock <email@hidden>
References: 
 >Since Xcode 3.0, ld insists on linking CoreData.framework (From: Jerry Krinock <email@hidden>)
 >Re: Since Xcode 3.0, ld insists on linking CoreData.framework (From: Chris Espinosa <email@hidden>)
 >Re: Since Xcode 3.0, ld insists on linking CoreData.framework (From: Jerry Krinock <email@hidden>)
 >Re: Since Xcode 3.0, ld insists on linking CoreData.framework (From: Jerry Krinock <email@hidden>)
 >Re: Since Xcode 3.0, ld insists on linking CoreData.framework (From: Chris Suter <email@hidden>)
 >Re: Since Xcode 3.0, ld insists on linking CoreData.framework (From: Jerry Krinock <email@hidden>)
 >New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved (From: Jerry Krinock <email@hidden>)
 >Re: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved (From: Jonathan Hess <email@hidden>)
 >Re: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: documentation window and "Previous"
  • Next by Date: Re: documentation window and "Previous"
  • Previous by thread: Re: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved
  • Next by thread: Re: New "Feature"? Was: Since Xcode 3.0, ld insists on linking...Resolved
  • Index(es):
    • Date
    • Thread