• 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: Paul Walmsley <email@hidden>
  • Date: Mon, 28 Nov 2005 21:55:21 +0000


Am I the only one who got problems with XCode not taking into account
dependencies very well ?
If I got 3 static library project A, B and C, where A use B which use C,
if I modify C and build A, C is rebuild but B and A are not linked to
the new versions.



It isn't clear (at least to me) how you have your dependencies actually configured in your project. Also what is linking to what? You have something using the static libraries in this project?

Finally you see this with "Debug" or "Release" style build
configurations or both?


This is the same bug we mentioned in a thread last week (followed by
thunderous silence :-)
http://www.cocoabuilder.com/archive/message/xcode/2005/11/25/1472

The situation as I've found it as where you have a command line
executable (eg via the C++ tool template) that statically links against
a couple of libraries that are listed as sub-project dependencies.
Modifying any file in one of the sub-projects causes that library to be
rebuilt but the linking phase is omitted.  You have to manually delete
the executable in order to force a relink.  It doesn't seem to make any
difference whether it's debug or release.  Zerolink is off.

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.

_______________________________________________
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 in XCode 2.2
      • From: Chris Hanson <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>)

  • Prev by Date: Is there a "Jump to where I was"?
  • Next by Date: Re: /Library/Caches/com.apple.Xcode.<UID> is huge!
  • 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