Re: Xcode and "subprojects"
Re: Xcode and "subprojects"
- Subject: Re: Xcode and "subprojects"
- From: "Torsten Curdt" <email@hidden>
- Date: Sun, 7 Dec 2008 03:30:39 +0100
> If you're using Xcode 3.1.1 or later,
I am on 3.1.2
> 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.
Well, that's not what I am after. That seems to be more or less the
same as my first simple scenario. Building 'MyProject' will not build
'MyCommon' as well (if necessary)
> What's probably happening now is that MyProject is depending on a
> build-and-install of MyCommon,
Well, the xcodeproj is showing up inside 'MyProject'. And 'MyCommon'
is added as a direct dependency to the target.
Not sure that is what you mean with "build-and-install".
> 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.
I doubt that's the problem. Both builds are in Debug mode.
After some back and forth I came across a very strange behavior:
The above project dependency failed reproducibly. I then added the
final framework of 'MyCommon' to 'MyProject' as well. (So it had a
dependency to both: The full Xcode project and the result of the
'MyCommon' build. That built fine. I then removed all dependencies to
'MyCommon'. Removed the 'build' directories and even restarted Xcode.
But just adding the Xcode project of 'MyCommon' to 'MyProject' was
enough and it just worked.
I am very puzzled about this. I could say I am happy that it works
now. But I will keep any eye on this.
Too bad that the project wasn't under source control for the test.
Well, next time.
cheers
--
Torsten
_______________________________________________
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