• 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
Common build folder still required?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Common build folder still required?


  • Subject: Common build folder still required?
  • From: "infinite labs" <email@hidden>
  • Date: Sun, 5 Oct 2008 16:47:07 +0200

Hello everyone.

I have a bunch of complex interaction between projects in my
repository; in particular, I have a number of interproject
dependencies. This allows me, for example, to pull a component from
project A, a component from project B and combine them into an
installer and place them into a DMG from a separate "packaging"
project.

Now, until recently, this required a common build folder. Now, for
unrelated reasons (automated building here I come!) I'm restructuring
the way the projects are stored and built, and I was hoping I could
move the projects away from a common build folder scenario. It was
mentioned to me that 3.1.1 lifts this restriction. In particular, I
figured I'd use source roots, make the project references relative to
the source roots in the packaging project and finally separate them
for good.

Am I going to run into any gotchas doing this? I'd like to know
beforehand, because this is going to require a decent amount of work.

 - ∞
 _______________________________________________
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

  • Prev by Date: Copying of resources
  • Next by Date: Using guardmalloc
  • Previous by thread: Re: Copying of resources
  • Next by thread: Using guardmalloc
  • Index(es):
    • Date
    • Thread