• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to configure Subversion to work with Xcode?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to configure Subversion to work with Xcode?


  • Subject: Re: How to configure Subversion to work with Xcode?
  • From: Jack Repenning <email@hidden>
  • Date: Thu, 17 Apr 2008 20:14:00 -0700

On Apr 17, 2008, at 7:42 PM, Juan Dent wrote:

One question: how are you setting the SCM dialog's parameters in Xcode?

Which version of Xcode are you using? Both 2.4 and 3.0 have some difficulties surrounding project creation. If someone else can make this clearer, I know I for one would be grateful, but so far as I can tell, both versions essentially require you to do something like this:


1. create the project (using Xcode, of course) in plain file space, not the SVN-managed area, and not your usual place for Xcode projects

2. import those files into your repository using some other SVN tool

3. At this point, the procedure splits, depending on Xcode version:
3.1. With Xcode 2.4, you need to hand check out the project somewhere (use some SVN client other than Xcode), then open the *.xcodeproj in Xcode. After that, it handles version control operations well.
3.2. With Xcode 3.0, you can do that, or you can use the Xcode "Repositories" window to do this check out. After that, it handles version control ops well ... even better than 2.4.


When Subversion 1.5 comes out, Subversion will allow a "checkout -- force" command. This has several potential uses (including fixing versioned packages), but in our context, it can be used to turn your non-versioned, Xcode-created project tree into a versioned one. I don't know if/when Xcode will be trained to use "--force", but when it does, the procedure could be simplified to:

1. Use Xcode to create the project in the normal place you expect it to be
2. Use some other tool to import it into the repository
3. Use "checkout --force" (in or out of Xcode) to morph your original project into a SVN-managed tree
4. Now Xcode handles the rest well



-==- Jack Repenning email@hidden Project Owner SCPlugin http://scplugin.tigris.org "Subversion for the rest of OS X"


_______________________________________________ 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
References: 
 >Re: How to configure Subversion to work with Xcode? (From: Juan Dent <email@hidden>)

  • Prev by Date: Re: How to configure Subversion to work with Xcode?
  • Next by Date: Re: Suppressing warning
  • Previous by thread: Re: How to configure Subversion to work with Xcode?
  • Next by thread: Using STL strings and supporting 10.2.x
  • Index(es):
    • Date
    • Thread