Re: Problem Building FW as a Sub-Project Reference
Re: Problem Building FW as a Sub-Project Reference
- Subject: Re: Problem Building FW as a Sub-Project Reference
- From: Karl Moskowski <email@hidden>
- Date: Thu, 28 Jan 2010 20:42:38 -0500
On 2010-01-28, at 8:34 PM, Chris Espinosa wrote:
> The general pattern is to use a shared build directory. But recent versions of Xcode should work correctly even if the two cross-related projects (note: there are no sub-projects in Xcode) have separate build directories. Just make sure that the framework reference that's in the app's Link and Copy Files build phases is the built product from the framework product's target, not an absolute reference. Just delete the Zipkit framework reference from the App project; rebuild the framework; then disclose the framework project's icon in the Groups and Files tree, then drag the framework product icon into the application target's Copy Bundle Resources and Link Binary with Libraries build phases:
>
> <PastedGraphic-1.png>
>
> This should work in Xcode 3.2 and later.
Thanks, Chris.
Does the project have to be set to Project Format: Xcode 3.2-Compatible ?
----
Karl Moskowski <email@hidden>
Voodoo Ergonomics Inc. <http://voodooergonomics.com/>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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