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: Rob Lockstone <email@hidden>
- Date: Mon, 07 Dec 2009 17:32:21 -0800
I do not know if this is still a requirement with the most recent version of Xcode, I do it now out of habit and because I access the same project on different machines. The requirement is (used to be?) that you must have the *project* file itself committed to whatever repository you're working with.
For example, I might have a project file (which is actually a directory) called .myproject.xcodeproj. I prefix it with a '.' so that it won't show up in other co-worker's file lists who don't use Xcode and don't want to see my project file, but that's just me. Anyway, within .myproject.xcodeproj is a file called project.pbxproj. That file is committed to the repository. Without it being there, previous versions of Xcode (and perhaps the current one) will not work with the other files in the repository even if you have everything else configured properly. Btw, there's also a couple other files in that .myproject.xcodeproj directory, but those are specific to the machine/account you're working on and don't need to be in the repository (stuff like window positions, which files you have open when you close Xcode, etc).
Hope that helps.
Rob
On Dec 7, 2009, at 15:23 , Brian Zwahr wrote:
> Ok, I'm re-opening this. I finally got around to getting Snow Leopard and the latest XCode. I still cannot do what I would like to, and want to get confirmation from the community that XCode does not, in fact, do what I'm looking for.
>
> Bad grammar in the above sentence aside, let me reiterate my situation and expectation.
>
> 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.
>
> 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.
>
> 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).
>
> 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 hope this makes sense. If not, I can try to be more clear or explain better.
>
> On Aug 30, 2009, at 3:18 PM, Joar Wingfors wrote:
>
>>
>> On 21 aug 2009, at 20.49, Joar Wingfors wrote:
>>
>>>> I tested creating a new project and adding the whole project to a blank svn repository. This resulted in me getting information and results with SCM in Xcode. However, I'm still unable to have a project that is just on my laptop (not in version control), add files to the project that have been checked out from subversion, and get SCM to work. Is this even possible? It seems unnecessary to have to have the entire project folder in version control to be able to have any part of the project able to give SCM information.
>>>
>>> Xcode 3.1 only supports selecting parent folders of the project.
>>
>>
>> Closing the loop on this recent thread:
>>
>> The recently released Xcode 3.2 removes the restriction that I mentioned above, and it also allows you to specify *multiple* SCM root folders in case you pull sources from several different places.
>>
>> 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