Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
- Subject: Re: Is XCode 3 SCM more dysfunctional than ever or am I doing something wrong?
- From: Jeff DuMonthier <email@hidden>
- Date: Sun, 25 Nov 2007 16:39:47 -0500
On Nov 25, 2007, at 4:02 PM, David Dunham wrote:
On 25 Nov 2007, at 12:44, Jeff DuMonthier wrote:
What is the project root? (You never needed to set this before.)
In the past, Xcode was happy using its anemic SCM abilities on any
file that was in the project. Now it seems to exuberantly -- but
exclusively -- offer its helpful abilities on ALL files in the
project root.
I'm not entirely sure what a project root is (unless it is the
folder containing the project, which is the root of my hierarchy)
but I think this is what I am seeing. Files that come as part of
the hierarchy with the project from the same repository (i.e. the
hierarchy in the working directory matches the repository) get
handled. Files that come from other repositories (or possible from
other points in the hierarchy from the project repository) only get
handled on a per file basis when you manually force XCode to do
so. Otherwise they are ignored for SCM.
You may want to set a higher project root then. It's in the General
tab of Project Info.
Ok. I see it now. The project root is the folder with the project in
it (which I guess is the default). All files are contained in that
folder, but some files in the working copy are not in the project
repository because they come from other repositories.
For many of us, this is not what we want, as the root is so bushy
as to slow things down. Except that without being rooted in the
root, a file can't be SCMed.
Which is pretty much useless unless your entire code base is a
contiguous subset of the hierarchy of one repository. I have a
separate repository for projects and project specific files, a
separate repository for common utility code and another for more
specialized modules that still may be shared among multiple projects.
You probably need to file a bug then. (Our case is a single
repository, but Xcode's new behavior is still problematic.)
It's hard to believe I'm the only one using code from multiple
repositories, unless the intention is to have everything organized in
frameworks, each with their own project, and each from a single
repository. That might work, but it's very XCode centric and would
make it a pain to integrate non-Mac specific code. And if that is the
case, why does it let me define multiple repositories in a project?
_______________________________________________
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