• 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
Project dependencies
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Project dependencies


  • Subject: Project dependencies
  • From: Jim Geist <email@hidden>
  • Date: Tue, 27 Aug 2013 22:38:58 -0700

I have a system that has several targets and some shared code. It is organized as a main application which was created with the initial workspace, several projects of static libraries which contain shared code between the main app and a utility app, and a project for the utility app. (There will eventually be more tool projects sharing the same libraries.)

For the main application, I was able to add the static library projects as target dependencies. However, when I click to add target dependencies to the utility app, none of the other projects or targets show up as addable.

I have a theory that this might be because the utility app is a child of the workspace/main app, and is therefore a sibling of the static libraries.

Does anyone have a suggestion as to how to structure the workspace so that this will work?

Thanks!!



 _______________________________________________
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: Project dependencies
      • From: Lasse Jansen <email@hidden>
    • Re: Project dependencies
      • From: Quincey Morris <email@hidden>
  • Prev by Date: Re: Building a large framework
  • Next by Date: Re: Project dependencies
  • Previous by thread: Re: Building a large framework
  • Next by thread: Re: Project dependencies
  • Index(es):
    • Date
    • Thread