Re: Inter-project dependencies
Re: Inter-project dependencies
- Subject: Re: Inter-project dependencies
- From: James Milne <email@hidden>
- Date: Thu, 22 Dec 2005 01:03:30 +0000
On Thursday, December 22, 2005, at 00:51AM, Daniel Jalkut <email@hidden> wrote:
>James - with the caveat that I've not reviewed your email too
>carefully, let me throw out a few points:
>
>1. Inter-project dependencies seem to require that you set the "Build
>Locations" settings for all projects involved to the same locaiton.
>
>2. Simply adding the subsidiary project and checking its product as
>part of a "super project" will not cause the desired dependency
>chain. You have to click the "super project" target you want to
>"depend on" the subsidiary, open its Inspector window, click the
>"General" tab, and then in the lower left corner click the + icon to
>add a dependency. At this point the built product you select shows up
>inside the target, as a sort of "pseudo-build phase."
>
>3. Even when everything works - sometimes it doesn't. I've observed
>from time to time that, especially while getting the kinks ironed
>out, you have to open a subsidiary product and manually build it.
>
>Maybe these oblique blows toward solving your problem will be of some
>help :)
Number 2 seems to have been the key step I was missing. I've added the output from those two projects as a direct dependency of my final application, and Xcode wires everything else up correctly.
Still have a couple of linking issues, but it's largely doing what I was wanting now :-)
Thanks!
--
Kind regards,
James Milne
_______________________________________________
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