• 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: Circular target dependency problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Circular target dependency problem


  • Subject: Re: Circular target dependency problem
  • From: Shaun Wexler <email@hidden>
  • Date: Fri, 27 Jan 2006 11:21:20 -0800

On Jan 27, 2006, at 8:26 AM, Timothy J. Wood wrote:

BUNDLE_LOADER is useful for any bundle where the app itself exports an API. Often you'll have a framework that the app and bundle both link, but not always.

Yes, that's how I'm using it. Framework code was moved into the Tiger-based app for efficiency.


  At any rate, one solution to this is to have three targets:

	- App
	- Bundles
		- Depends on app
	- Build Package
		- Does the copy into the app

Yes, that's how I'd attempted to do it. ;)

JPEG image



The dependency error occurs on the copy phase, which is simply a new Copy Files target that has 3 copy phases to move all of the built products into the app package. The app and bundles are first built with an Aggregate target. Possibly a bug in Xcode?

This isn't nearly as pleasant as having Xcode realize the difference between a linking dependency and packaging dependency. There is no circular dependency if the dependency graph splits these two concepts. Link dependencies should be rooted in the 'libraries and frameworks' phase and packaging dependencies in the 'copy files' phases. Then, Xcode could notice that it has a packaging dependency on X.bundle and that it has a target which will build X.bundle, and recurse to build it. Since X.bundle doesn't have a link or package dependency on the app, no circular dependency would be flagged.

Building target “Package” of project “MacFOH” — (5 errors)
Checking Dependencies
File /Users/shaun/Projects/MacFOH/build/G3.plugin depends on itself. This target might include its own product.
File /Users/shaun/Projects/MacFOH/build/G4.plugin depends on itself. This target might include its own product.
File /Users/shaun/Projects/MacFOH/build/G5.plugin depends on itself. This target might include its own product.
File /Users/shaun/Projects/MacFOH/build/SSE.plugin depends on itself. This target might include its own product.
File /Users/shaun/Projects/MacFOH/build/MacFOH.kext depends on itself. This target might include its own product.
Build succeeded (5 errors)
--
Shaun Wexler
MacFOH
http://www.macfoh.com


"Problems cannot be solved by the same level of thinking that created them." - Albert Einstein


 _______________________________________________
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

References: 
 >Circular target dependency problem (From: Shaun Wexler <email@hidden>)
 >Re: Circular target dependency problem (From: Chris Espinosa <email@hidden>)
 >Re: Circular target dependency problem (From: "Timothy J. Wood" <email@hidden>)

  • Prev by Date: Re: Transitioning to XCode 2.2.1 problems...
  • Next by Date: Universalizing jnilib...
  • Previous by thread: Re: Circular target dependency problem
  • Next by thread: Can you use Intel Assembler syntax with xCode 2.2?
  • Index(es):
    • Date
    • Thread