Re: Xcode 3.2 snaphots with code shared by multiple projects
Re: Xcode 3.2 snaphots with code shared by multiple projects
- Subject: Re: Xcode 3.2 snaphots with code shared by multiple projects
- From: Joar Wingfors <email@hidden>
- Date: Sat, 10 Oct 2009 02:02:49 -0700
On 9 okt 2009, at 19.07, David Gimeno Gost 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?
Please file a bug report asking for improved / updated documentation:
<http://developer.apple.com/bugReporter/>
Thanks,
j o a r
_______________________________________________
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