• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Three Level Dependencies between xcode projects still fails in XCode 2.2


  • Subject: Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
  • From: Chris Hanson <email@hidden>
  • Date: Mon, 28 Nov 2005 15:04:12 -0800

On Nov 28, 2005, at 1:55 PM, Paul Walmsley wrote:

So we have 3 xcode project files - A.xcodeproj, B.xcodeproj and
C.xcodeproj. The first two each contain a single target - static libs
A and B. The last one contains a single executable target C. The C
project has dependencies on A.xcodeproj and B.xcodeproj and the C target
links against the A.a and B.a libraries. There's also a cpp file that
defines main() and calls functions in libs A and B.

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.

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.

  -- 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


  • Follow-Ups:
    • Re: Three Level Dependencies between xcode projects still fails inXCode 2.2
      • From: "James Larcombe" <email@hidden>
    • Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
      • From: Olivier Tristan <email@hidden>
References: 
 >Three Level Dependencies between xcode projects still fails in XCode 2.2 (From: Olivier Tristan <email@hidden>)
 >Re: Three Level Dependencies between xcode projects still fails in XCode 2.2 (From: Shawn Erickson <email@hidden>)
 >Re: Three Level Dependencies between xcode projects still fails in XCode 2.2 (From: Paul Walmsley <email@hidden>)

  • Prev by Date: Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
  • Next by Date: Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
  • Previous by thread: Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
  • Next by thread: Re: Three Level Dependencies between xcode projects still fails in XCode 2.2
  • Index(es):
    • Date
    • Thread