Re: embedding private frameworks in Xcode 2.1
Re: embedding private frameworks in Xcode 2.1
- Subject: Re: embedding private frameworks in Xcode 2.1
- From: Fritz Anderson <email@hidden>
- Date: Fri, 17 Jun 2005 11:06:10 -0500
On 17 Jun 2005, at 10:31 AM, Jesse Grosjean wrote:
Next in the embeddingFrameworks.mov tutorial it says to drag and
drop MyFramework.framework from the build directory of the
MyFramework.xcodeproj project into the Linked Frameworks folder of
the MyApp project. The problem is that as of Xcode 2.1 there are
multiple locations for this file (Debug, or Release). I'm not sure
which to use and ideally I would like to use the Debug version when
I'm compiling MyApp in debug configuration and the Release version
when I'm compiling my app in Release configuration. This is
especially important for the copy frameworks build phase, I want
the framework with the matching configuration added into my app
bundle.
7. To get around this problem I'm NOT placing MyFramework.framework
in the "Linked Frameworks" folder. Instead I've found that in
MyApp's "Groups & Files" pane there is a draggle reference to
MyFramework.framework under the referenced MyFramework.xcodeproj
project. I can drag this into the MyApp target's "Link Binary With
Libraries" and this "Copy Files" build phases.
This does seem to work, but I haven't seen it documented anywhere,
it also seems to require that both projects use the same location
for "Place Build Products In".
This is in every respect correct.
Interdependent projects should build to the same build folder.
Dragging the product of a dependency project to the linkage and copy-
files phases is the right way to insert it in those phases. It
adjusts for build configuration.
-- 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