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: Brian Zwahr <email@hidden>
- Date: Tue, 25 Aug 2009 13:07:24 -0500
On Aug 25, 2009, at 10:31 AM, Jeremy Pereira wrote:
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.
That makes sense. I will look into it. I am also using 1.6 from
Collabnet, and prior to that, I was using 1.6 installed from Gentoo's
Mac OS X portage prefix.
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?
I can think of two cases.
1.) You have a project (in my case, a PHP application) that you
develop from multiple machines at different locations using programs
other than Xcode (i.e. Xcode on the Mac at home, emacs on the
workstation at work, some other program somewhere else, etc). The
Xcode project does you no good except on the Mac running Xcode.
However, if you only had the files (in this case, php files) and not
the project stuff under version control, then you could just have
working copies of the files on all the machines and work on them no
problem. Also, along with this, if the project (like all of mine) are
started in a non-Xcode environment, you don't have the Xcode project
at all in version control (which is where I'm at now). Then, when you
decide to try to continue development on a Mac using Xcode (but will
still be developing in the other environment), you don't get any
version control information, because even though the files are checked
out and have the information there (i.e. the .svn directories), Xcode
won't read that information unless the entire project is under version
control.
2.) What if you have multiple individual components developed, each in
their own version control repository (as they should be), then you
want to use them in a new project, also under version control. It
seems like you would have to check them out, add them to the new
project, commit them to version control in the new project, and then
you have two different versions of it in version control. If you were
to update one of the components, you would have to update it in the
new project's repository *and* in the component's repository. That
could spell disaster if that component was being used in multiple
projects.
_______________________________________________
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