• 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
Proper way to deal with dependent projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Proper way to deal with dependent projects

  • Subject: Proper way to deal with dependent projects
  • From: Paul Haddad <email@hidden>
  • Date: Tue, 11 Nov 2003 13:48:48 -0600
Hi All,

I've got two projects one being a common Framework used by several applications and the other being an application itself. I noticed that XCode allows me to drag a project onto another and make it a dependency. This seems to work for the most part but it doesn't seem like the settings (build location, build style) of the parent project are propagated down to the child project. Is there a fix for this?

If not what are other folks doing? I'm thinking I'll end up having to write a Shell Script target and call xcodebuild on the child project with the build style selected and some env. vars set. But hope there's a better way.
---
Paul Haddad (email@hidden)
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
  • Prev by Date: Re: Customizing variable's summary
  • Next by Date: Support for a Script Menu?
  • Previous by thread: Re: Adding own languages
  • Next by thread: Support for a Script Menu?
  • Index(es):
    • Date
    • Thread