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: Joar Wingfors <email@hidden>
- Date: Tue, 8 Dec 2009 08:34:53 -0800
On 7 dec 2009, at 15.23, Brian Zwahr wrote:
> I have a PHP application that I've built using emacs, which is under version control in a subversion repository. I have a working directory checked out, let's say, in ~/svn/app/trunk. When I open said file in emacs (or run M-x svn-status) I get version control information, and when I make a change, the modified state is shown in emacs and I can commit the change from emacs.
You maintain a product type that isn't supported by Xcode, and you edit and debug it outside of Xcode. I'm a bit curious as to why you want to manage SCM through Xcode?
> I am trying to replicate this in XCode. Here's what I do. I open XCode, start a new "other" (blank) project. I have the subversion repo added to my Repository List in XCode. I check out a copy of trunk (which I shouldn't have to do, since I already have one checked out for working in emacs, but I figured I'd start fresh doing *everything* in XCode). So now I have a checked out working directory and a new, blank XCode project.
You certainly would not have to check out the project from Xcode. There's nothing special in how Xcode checks out projects from SCM.
> No matter what I do, I cannot get the working directory into the project in such a way that I get version control information or functionality. For instance, if I add existing files to the project and select the trunk directory, I get the trunk directory structure and files in the left bar of XCode (adding by reference, not copying), but I see no svn information (modified, added, etc). If I set up a root to the trunk directory and select the correct repo from the repository list to go with it, I still do not get version control information or abilities (diff, commit, update, etc).
You would not have to add your directories and files to Xcode to get SCM working. I think that it would make more sense for you not to, if you're not already using Xcode to manage your project and files.
> So, what I'm asking is do I have to add the whole project and project directory just get see the version control information of any files (even if they are already in a checked out working directory)?
I made a simple test this morning, and it worked just like I thought & hoped it would:
* Created a new project from the "empty project" template in Xcode 3.2.1
* Added a new project root for an already checked out working copy elsewhere on disk
* Removed the original SCM entry that pointed to the project directory
As soon as I had done that, I got status for the files in that working copy showing up both in "SCM > SCM Results" and in the SCM smart group in the Groups & Files pane. This shows that you do not have to have the project file checked in for SCM support to function. Not sure why this wouldn't work for you, but it seems to suggest that there's something that you're not doing that you should, or something that you're doing that you shouldn't...
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