Re: Adding existing svn files to new project
Re: Adding existing svn files to new project
- Subject: Re: Adding existing svn files to new project
- From: Jeremy Pereira <email@hidden>
- Date: Tue, 25 Aug 2009 16:31:12 +0100
On 24 Aug 2009, at 15:41, Brian Zwahr wrote:
I have tried every tutorial I've found, which is quite a few,
including the Apple docs and help files. Can you remember how you
changed the subversion client used by Xcode?
Xcode links directly to the subversion dynamic libraries. It doesn't
use the command line client at all. This can be problematic because
the default client is rather old (1.4.4) and if you use a newer one it
will update the working copies so that Xcode can no longer access them.
You need to make sure that Xcode looks in the right place for the
dylibs. I seem to have done that (I use svn 1.6 from Collabnet) but I
can't for the life of me remember how I did it.
I'm surprised that Xcode only supports SCM for parent project
folders. That seems unwise. Example: what if there were some classes/
files in one svn repository, other classes/files in another
repository, etc., and all of them were to be used in a new project?
Currently, you couldn't get working copies of each repository and
use them in a project, then be able to handle SCM for each one
inside Xcode. Sad, but I think I might see if I can find out
anything about upcoming Xcode releases or see if I can place a
feature request with Apple.
I guess Xcode works with projects and either the project is under
version control or it isn't, there's no halfway house. It's not a
problem that's ever bothered me because why would you not put the
whole project under version control?
_______________________________________________
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