• 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
Xcode and SCM
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode and SCM


  • Subject: Xcode and SCM
  • From: Keith Duncan <email@hidden>
  • Date: Wed, 13 Jun 2007 17:15:17 +0100

I'm using Xcode to manage all my projects, the number of which has grown sufficiently large that I need to consider some form of SCM. I have decided to go with Subversion and have already installed it, but I still have some questions as to how I should organise my projects/ SCM system.

My first question is how should I arrange my projects into repositories? Should I create a repository for each of my projects or have one global repository for all my projects? What are the pros and cons of each approach. Am I able to implement a shared code repository that allows me to keep my generic code is one place and accessible by all my other projects for checkout/commit? Xcode doesn't seem to allow it as each project can only be backed by one repository.

Another problem I have is that I have a assortment of small projects which I use to prototype classes outside the context of the app they were originally developed for, my shared code resources. Would it be best to back each individual project by SCM and have my Xcode projects refer to these shared files byref instead of copying them to their own source root? That would ensure that they are always built against the most recent working copy of the shared source, but would these files interfere with the app project's own SCM system? I wouldn't want multiple copies of the shared source files floating around, that's the issue I'm try to fix now. This approach would also mean that were the functionality of one of these shared classes change sufficiently to break another app, the other app couldn't roll back to a copy that did work for it and the code would have to change. This is unlikely to happen but I am trying to look ahead.

The online documentation I have found wasn't too enlightening, and has left me confused as to what SCM can and cannot do for me. Any help/ insight would be much appreciated.

- Keith
_______________________________________________
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


  • Follow-Ups:
    • Re: Xcode and SCM
      • From: Frederick Cheung <email@hidden>
  • Prev by Date: Re: Converting a Makefile project to Xcode
  • Next by Date: Compiling 64-bit
  • Previous by thread: Re: Unknown escape sequence '\/'
  • Next by thread: Re: Xcode and SCM
  • Index(es):
    • Date
    • Thread