• 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: Jerry Krinock <email@hidden>
  • Date: Mon, 10 Dec 2007 13:16:05 -0800


On 2007 Dec, 08, at 1:13, Jonathan Hess wrote:

I would guess that this is caused by the fact that your project is linking Cocoa.framework. Cocoa is an umbrella framework that includes Foundation.framework, AppKit.framework, and CoreData.framework.


Thanks, Jon. That makes so much sense that I decided to dig into my file archives, bring up the project version which I had used in Xcode 2.5 (that worked), and compare its list of frameworks to the list in the current project (that caused all the headaches).

Findings:

Both have framework Cocoa, with a checkmark indicating target membership:

    [x] Cocoa.framework

That doesn't corroborate your very sensible explanation, so I looked further. The newer project has framework CoreData, but it is not checked, indicating no target membership:

    [ ] CoreData.framework

and, indeed, as you can see from the Build Transcripts in my earlier posts, the CoreData framework was not linked, at least in the sense of a -framework argument to ld.

But the older project does not have CoreData.framework even listed.

I notice that when I create a new Cocoa Application in Xcode, it gets the Cocoa framework "in" the project ^and^ in the target (box checked). Also, it has the "component" frameworks Appkit, CoreData and Foundation "in" the project but ^not^ in the target (box not checked). The new, empty project still builds if I remove these three.

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?

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

Thanks,

Jerry
_______________________________________________
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: Chris Hanson <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>)

  • Prev by Date: Re: why aren't xibs the default?
  • Next by Date: Xcode crashes on breakpoints
  • 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