Re: Linked Frameworks, Other Frameworks, etc.
Re: Linked Frameworks, Other Frameworks, etc.
- Subject: Re: Linked Frameworks, Other Frameworks, etc.
- From: Fritz Anderson <email@hidden>
- Date: Sun, 17 Jun 2007 12:13:48 -0500
On 17 Jun 2007, at 11:14 AM, Jerry Krinock wrote:
When you add a framework to a project, it can go
"loose" in the "Frameworks" group, or
in the "Linked Frameworks" subgroup, or
in the "Other Frameworks" subgroup.
How do you decide where to put it?
The Frameworks group is, as you discover, completely free-form.
Placement within that group, or even into it at all, is not
automatic. It's up to you. Whatever pleases you. The groups don't
even have to exist at all.
The default layout layout for Cocoa-application projects is to have
Cocoa.framework in the Linked Frameworks group, and
Foundation.framework and AppKit.framework in the Other Frameworks group.
The rationale seems to be that the target doesn't link against
Foundation or AppKit; it links against Cocoa (which happens to
contain Foundation and AppKit). Apple puts it into the Linked group.
However, Foundation and AppKit are useful for reference, because
Xcode lets you open them up and examine the constituent headers. (A
file/framework can be part of a project, for reference, without being
part of any target.) Apple puts them into the Other group.
It's a sensible way to organize it. But you might, for instance, want
to add a group for "My Frameworks," or something.
— F
_______________________________________________
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