• 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
embedded projects, dependencies, and linking
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

embedded projects, dependencies, and linking


  • Subject: embedded projects, dependencies, and linking
  • From: Tobias Ford <email@hidden>
  • Date: Sun, 15 Jul 2007 17:36:37 -0500

Our suite of applications is built using a hierarchy of libraries that depend on their "parent" libraries.

For example, we have:

engine
	clientEngine (depends on sharedEngine)
		application
			FinalApplications
		library
			finalLibraries.a
	serverEngine (depends on sharedEngine)
		application
			FinalApplications
		library
			finalLibraries.a
	sharedEngine
		application
			FinalApplications
		library
			finalLibraries.a

game
	clientGame (depends on sharedGame)
		application
			FinalApplications
		library
			finalLibraries.a
	serverGame (depends on sharedGame)
		application
			FinalApplications
		library
			finalLibraries.a
	sharedGame (depends on sharedEngine)
		application
			FinalApplications
		library
			finalLibraries.a

When building the final applications, I'm stuck with libraries either having undefined symbols for their parents or running into multiple definitions that generate warnings. This appears to depend on the final application and what the libs tend to instantiate. In other word, If I trim the dependencies down for one app and then can't link another final application. I restore dependencies for another and generate warnings in others that were fine previously fine.

Does anyone know the best way (xcode wise) to set this up so there aren't any warnings in the final build? Is their a linker option that I should use?

I would prefer that the child libraries don't require linking against their parents in any situations and that the final applications instead link against all of the libraries that they reference. Unfortunately I haven't been able to arrange everything to get this to happen yet.

Thanks in advance.

-------------------
Tobias Ford...
tobias1482 'at' mac.com
tford 'at' spacetimestudios.com
-------------------
Sr Programmer @ space time studios for a generic space game mmo





_______________________________________________
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: embedded projects, dependencies, and linking
      • From: Tobias Ford <email@hidden>
  • Prev by Date: Re: Xcode Cocoa Framework templates
  • Next by Date: JavaCompiling.plist and _EOSomething.java files in nibs
  • Previous by thread: Re: Xcode Cocoa Framework templates
  • Next by thread: Re: embedded projects, dependencies, and linking
  • Index(es):
    • Date
    • Thread