• 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: Xcode 3.2 snaphots with code shared by multiple projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.2 snaphots with code shared by multiple projects


  • Subject: Re: Xcode 3.2 snaphots with code shared by multiple projects
  • From: David Gimeno Gost <email@hidden>
  • Date: Sat, 10 Oct 2009 04:07:40 +0200

On 10 Oct 2009, at 03:19, Joar Wingfors wrote:

Project roots control two things in Xcode: Snapshots and SCM.

Yes, I know (this *is* documented). SCM is one of the things I must take into consideration. What wasn't clear to me (because it *isn't* documented) is what the implications of setting the project roots one way or another actually are. The currently available documentation says:


"in projects that compose a larger project, you should set the project root at a directory that contains the subprojects. (This directory doesn’t have to contain all of the larger project’s subprojects, only the subprojects that you modify.) Following this practice avoids snapshot conflicts with files shared by more than one project."

Why would setting the project folder as the only project root cause any conflicts with files shared by more than one project? It seems to me that the conflicts might happen precisely as a result of including the shared files in the snapshots for all the projects that share them...

May I reliably use the project folder as the only project root if I don't want Library to be restored when I restore from a snapshot?

Sure.

OK, this is what I expected and wanted to be sure of. But why does the documentation warn that this might cause conflicts with files shared by more than one project then? What kind of conflicts is the cited paragraph talking about?


What would actually be restored from a snapshot depending on whether the project folder is the only project root or not, i.e. depending on whether Library is another project root or not?

Not quite sure what you're asking here.

I was wondering whether restoring from a snapshot does more than just restoring the contents of the project roots.


I think I was just confused by the documentation warning about potential conflicts. It seems things are as simple as one would expect, i.e. snapshots don't really save and restore the entire project state at a particular point in time, but just the contents of the folders specified as project roots -- which is what I want, BTW.

Thanks for clarifying this.

Regards.

_______________________________________________
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: Xcode 3.2 snaphots with code shared by multiple projects
      • From: Joar Wingfors <email@hidden>
References: 
 >Xcode 3.2 snaphots with code shared by multiple projects (From: David Gimeno Gost <email@hidden>)
 >Re: Xcode 3.2 snaphots with code shared by multiple projects (From: Joar Wingfors <email@hidden>)

  • Prev by Date: Re: Can't get Xcode to include correct string.h
  • Next by Date: Re: App linked on Leopard not starting on Tiger
  • Previous by thread: Re: Xcode 3.2 snaphots with code shared by multiple projects
  • Next by thread: Re: Xcode 3.2 snaphots with code shared by multiple projects
  • Index(es):
    • Date
    • Thread