Re: Xcode and "subprojects"
Re: Xcode and "subprojects"
- Subject: Re: Xcode and "subprojects"
- From: Chris Espinosa <email@hidden>
- Date: Sat, 6 Dec 2008 18:02:34 -0800
On Dec 6, 2008, at 5:29 PM, Torsten Curdt wrote: I need some help. I am scratching my head over this already for quite
a while and would like to find a way to finally fix this properly.
So I have a project 'MyProject' and a project 'MyCommon'. While
'MyCommon' is an embedded framework, 'MyProject' is using it. The
simple way it works just fine. I build 'MyCommon' and then drag the
built framework into 'MyProject', add it to be copied in the target
and I am done. All good.
Of course the above method always requires me to manually compile
'MyCommon' on changes. So it seems the better way is to just drag the
'MyCommon' project itself into 'MyProject'. Which sort of works. Added
as a dependency it does get compiled on changes. Unfortunately the
headers that get exported by 'MyCommon' are not available to
'MyProject' like this though.
They are marked as 'public' and are inside the framework. (Otherwise
the first method also wouldn't have worked)
So what could I be missing?
If you're using Xcode 3.1.0 or earlier, you need to set up a shared build directory so that MyProject can link to the build product of MyCommon in its build directory.
If you're using Xcode 3.1.1 or later, you need to remove the MyCommon.framework from the targets of MyProject, build MyCommon, and then re-add it from the list of products under MyCommon in the Groups and Files tree.
What's probably happening now is that MyProject is depending on a build-and-install of MyCommon, so when you do a Debug build of MyCommon into the build folder, MyProject picks up the older Release/Install build of MyCommon in its installed location.
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