Re: Xcode 3.1.1 Copied Framework != Linked Framework
Re: Xcode 3.1.1 Copied Framework != Linked Framework
- Subject: Re: Xcode 3.1.1 Copied Framework != Linked Framework
- From: Chris Espinosa <email@hidden>
- Date: Thu, 6 Nov 2008 11:51:28 -0800
On Nov 5, 2008, at 5:52 PM, Dominic Feira wrote: We're just going through the process of moving our build system over to Xcode 3.1.1. It seems that now when a framework from a dependency project is copied, it always copies the framework from the build location in that dependency.
This is not new; this is the way Xcode has always worked. We have a custom build script that copies dependencies into the root project's TARGET_BUILD_DIR. This copy is the one that built products links to. The one in the original dependency project is the one that is copied during the frameworks copy stage. For plugin development we have to massage some of the framework loader paths, which is done in the TARGET_BUILD_DIR prior to product linking. Of course now since the copy of the framework inside of the frameworks directory is not the one that had its loader path modified nothing links properly when the plugin is loaded. Is there a way to make Xcode link AND COPY the framework that is in the TARGET_BUILD_DIR? Copying doesn't respect the framework search path.
Not in one go. You generally have to do these three steps:
1) Set the loader path of the built framework 2) Link against the framework that has its loader path set correctly 3) Copy the framework into its destination
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