• 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: Two projects in one directory? (Solved?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Two projects in one directory? (Solved?)


  • Subject: Re: Two projects in one directory? (Solved?)
  • From: Scott Tooker <email@hidden>
  • Date: Mon, 1 Dec 2008 12:55:25 -0800


On Dec 1, 2008, at 12:12 PM, Fritz Anderson wrote:

On 1 Dec 2008, at 11:12 AM, Fritz Anderson wrote:

My book "Xcode 3 Unleashed" relies on being able to create two projects in the same directory. That is, one directory contains two .xcodeproj files.

This worked through Xcode 3.0.x, but the new method for creating projects doesn't allow for selecting a directory independently of the placement of the project file.

Am I right that there is no simple way to achieve the same thing? (I could make two directories and copy the contents, but that isn't simple.)

I think I know the answer, but I wanted to verify it before delving further.

And here is my further delving, though I'd be grateful for comments.

1. There's no way to create a second project in another project's directory. This is a good thing, because instantiating the second project's templates may create file-name collisions.

2. Having two projects in the same directory made sense if you wanted them to share a build directory. There are other ways to do that, but sharing the project directory was, through 3.0.x, the simplest way to do it.

3. However, Xcode 3.1.x is much smarter about finding the products of dependent projects. The shared-build-directory workarounds are no longer necessary. Put the two projects' directories anywhere you like (one inside the other simplifies SCM), set up the dependencies as before, and everything should work.

Is this the right approach?

There are a number of other reasons why #3 is a good direction to pursue. However, I'd suggest filing a bug on not being able to create a second project in the same directory (since there are also good reasons to be able to do that).


Scott



	— F

_______________________________________________
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

_______________________________________________ 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: 
 >Two projects in one directory? (From: Fritz Anderson <email@hidden>)
 >Re: Two projects in one directory? (Solved?) (From: Fritz Anderson <email@hidden>)

  • Prev by Date: error from strip tool
  • Next by Date: Re: Libraries switch binary to "ppc7400" how do I force it back to "ppc".
  • Previous by thread: Re: Two projects in one directory? (Solved?)
  • Next by thread: Xcode and creating a library project
  • Index(es):
    • Date
    • Thread