Re: Three Level Dependencies between xcode projects still fails inXCode 2.2
Re: Three Level Dependencies between xcode projects still fails inXCode 2.2
- Subject: Re: Three Level Dependencies between xcode projects still fails inXCode 2.2
- From: "James Larcombe" <email@hidden>
- Date: Tue, 29 Nov 2005 10:59:16 -0000
Chris Hanson wrote:
This is how I've mentally broken down the above, numbered for easy
reference:
1. A.xcodeproj contains TargetA which builds libA.a
2. B.xcodeproj contains TargetB which builds libB.a
3. C.xcodeproj contains TargetC which builds commandC
4. C.xcodeproj contains a reference to A.xcodeproj
5. TargetC in C.xcodeproj links against libA.a
6. C.xcodeproj contains a reference to B.xcodeproj
7. TargetC in C.xcodeproj links against libB.a
My question is, is the following information also set? It's not
clear from your description above whether this is the case. This
information is specified in the Dependencies pane of the General tab
of the info window for a target.
8. TargetC in C.xcodeproj has a dependency on TargetA in A.xcodeproj
9. TargetC in C.xcodeproj has a dependency on TargetB in B.xcodeproj
The information in #8 is not derived automatically from #4, and #5;
it must be specified explicitly.
Yes, we do have the dependencies set correctly for the target in the
top-most project (TargetC in commandC, in your example).
However, I would expect not having #8 or #9 to give you the opposite
problem from what you report -- that if you change a file used to
build libA.a, libA.a isn't rebuilt when you build TargetC.
Yes, exactly. It's strange that it's rebuilding the subprojects, but not re
linking with their output.
James
_______________________________________________
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