Re: Xcode 3.0 and new SCM features
Re: Xcode 3.0 and new SCM features
- Subject: Re: Xcode 3.0 and new SCM features
- From: Jean-Daniel Dupas <email@hidden>
- Date: Wed, 12 Nov 2008 14:18:46 +0100
Le 12 nov. 08 à 14:09, Jean-Daniel Dupas a écrit :
Le 12 nov. 08 à 13:08, Marc Stibane a écrit :
Am 08.01.2008 um 21:01 schrieb Andrew Pontious:
On Jan 8, 2008, at 6:48 AM, Jake Traynham wrote:
I'm trying to figure out how to get back functionality from Xcode
2.5 and previous with the SCM stuff. I have a CVS repository
that looks similar to this:
/CVS/Common/
/CVS/Project1/
/CVS/Project2/
Both "Project1" and "Project2" use code from the "Common" code
directory. In Xcode 2.5 and before, the SCM feature was able to
figure out when code in the "Common" directory had changed and
allowed me to update/commit/etc that code. Now in Xcode 3.0, it
doesn't see those changes and the context menu for files in the
"Common" directory show "Add to Repository" as if they aren't
already. I tried changing the "root" of the project to my main /
CVS/ directory, but when I do that, I see *all* the changes for
every project in the CVS directory. I also tried adding a
symlink to the Common directory under the Project directories to
see if that would help, but it didn't.
Does anyone have any pointers or suggestions on how to get back
this functionality where the SCM pane shows all changes to files
in (and only in) the current Project's directory and the Common
code directory? This seems simple enough.
In Xcode 2.*, Xcode's SCM system would go through all the files in
your project, figure out their location, and figure out if those
locations were under some sort of SCM system that it could detect.
As you can imagine, this could take a lot of time and resources.
Sure, but...
For Xcode 3.0, we switched to a system based on the new Xcode
project root. You specify one SCM system and location for your
project, and that is used to evaluate every file under your
project root.
Common, guys - haven't you ever seen a company with more than 10
developers?
I just recently started working for a company where there are more
than 100 co-workers.
They have a CVS (urgh, never change a running system, you know)
tree like this
/data
cvstree
proj <- project management files here
iphone
linux
mac
sun
win
unix
vms
...
make <- make files for automatic builds here
linux
unix
...
src
*several dozen subdirs*
*several thousand source files*
Compiling *all* takes at least 2-3 days per platform, even on
dedicated compile machines. Nightly builds? Usually we compile
twice a week, with a snapshot copy from the cvstree.
And of course, I only need a *few* files from *some* of those src-
subdirs for my iPhone project - and there are some thousand other
source files which I do not need, and definitely don't want Xcode
to look at, cause every few seconds one of my co-workers checks in
something...
We realize that this shuts out the kind of functionality that
you're looking for, and I apologize for that. We are looking into
potential solutions for future versions of Xcode.
Since I am coding for the iPhone, I have to use Xcode 3.1 -
otherwise I'd use Xcode 2.5 as the Mac developers do.
PLEASE, give us back the file based SCM system, at least as an
option.
In our case this would surely take "a lot LESS of time and
resources" than the new Root folder based system.
Don't need everything ? do a sparse checkout. ( http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html
)
That said, I don't think this feature is available on CVS.
And even if you use SVN, this is an svn 1.5 features, so you should
update the system version to use it. (search this list archives to
find how to do this: http://www.cocoabuilder.com/archive/message/xcode/2008/10/3/24998
)
_______________________________________________
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