• 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: Subversion with xcode problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subversion with xcode problems


  • Subject: Re: Subversion with xcode problems
  • From: William Kitching <email@hidden>
  • Date: Sun, 1 Mar 2009 22:24:09 +0000

Ok things seem to be working now, thanks for the help on this.


On 1 Mar 2009, at 14:23, Paul Walmsley wrote:

Quincey Morris wrote:
On Feb 28, 2009, at 14:21, William Kitching wrote:

At this point I was happy and things seemed simple enough, so I went ahead and deleted my test Subversion repository & test application. I then created my 'real' repository and I uploaded all of my source from my development root folder. I then re- configured the SCM in xcode and it seemed happy enough.

My complications start here as I'm having difficulty getting xcode to realize there are changes between my local machine and the server. There is no letter 'M' (local modified file) appearing to the left of my source file. After many hours of tinkering I found my xcode project needs to mirror the root of my repository or it doesn't work correctly.

It's not clear from your description whether you already figured this out, but the "gotcha" in starting to use Xcode for SCM is that after you've uploaded your source (via Xcode's repository Import function), you must discard that source and check out fresh copies from the newly-populated repository. Otherwise, Xcode doesn't realize that your local copies are actually related to the contents of the repository.
It does sound like this may be the case, so this wouldn't be an Xcode issue at all. Subversion itself won't recognise that your directory is linked to the repository. One way to find out whether this is the case is start a terminal window, change to your source directory and type 'svn info'. If you get an error "svn: '.' is not a working copy" then this will confirm that you haven't yet checked out your source.

In general the workflow in importing your sources to SVN is:
- import your source tree
- move the directory aside
- checkout the source tree

Paul

_______________________________________________
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



___________________________________________________________ All New Yahoo! Mail – Tired of Vi@gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html


_______________________________________________
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: Subversion with xcode problems
      • From: "Eric A. Borisch" <email@hidden>
References: 
 >Re: Subversion with xcode problems (From: Paul Walmsley <email@hidden>)

  • Prev by Date: Re: does Leaks instrument not work correctly with C++?
  • Next by Date: Re: does Leaks instrument not work correctly with C++?
  • Previous by thread: Re: Subversion with xcode problems
  • Next by thread: Re: Subversion with xcode problems
  • Index(es):
    • Date
    • Thread