macOS Setting up SVN and Xcode

Eraserhead said:

I have decided to make my program open-source and to allow other people to contribute want to setup SVN.

Click to expand...

First you need a server that is on the public internet. SVN is not so usfull if others can't get to it. You best option is to get an account on Source Forge. They offer free acounts to open source projects and provide CVS (I don't think they use SVN?) email lists, web space and a bug tracking system. Everything you will need. Much better to use their service then set up you own. Also when peole are searching for a project they might think to search Source Forge but would never in a million years think to look on your server
http://sourceforge.net/

Google Code can host your project. They have SVN. It is pretty nice. Smoother and easier to setup than Source Forge. I am going to be moving all my code to it soon.

http://code.google.com/hosting/createProject

As for using SVN in Xcode, check out

http://maczealots.com/tutorials/xcode-svn/

It's actually easy to setup and figure out pretty fast.

I do not believe Xcode can do checkouts. So I think you have to do that with Terminal:


You will probably have to add your .xcodeproj to the repository:


Then you should be able to open your Xcode project, Get Info on your project in the Groups & Files column, and then enable it:

View attachment 74469

Then right-click the Groups & Files column, and check SCM. That will show the Subversion status of each file in your Xcode project.

View attachment 74470

I've had nothing but trouble with any SCM system and Xcode. But it's fixed in Leopard w/Xcode 3. Very simple, very usable.

GeeYouEye said:

I've had nothing but trouble with any SCM system and Xcode. But it's fixed in Leopard w/Xcode 3. Very simple, very usable.

Click to expand...

I look forward to Xcode 3.

I have had problems with Xcode and SCM (Subversion) too. I think I've nearly narrowed down the cause for the problem I'm having though. It seems if I add a directory by reference (blue folder icons rather than yellow) which is not source code managed, ie not in a repository, then Xcode will loose track of which source files have been updated or are out of date. For example if I modify a file then it shows up as modifed in the SCM list as you would expect. If I then quite Xcode then go back in, that same file is no longer flagged as modified. No matter how many times I hit 'refresh project' Xcode will not see that file as modified. If I delete the referenced folder (which has is not attached to any repository) then Xcode will see the modified file and everything works as you would expect.

b e n

I only ever use SVN in Xcode to look at revision comments and using FileMerge. Everything else I just feel more comfortable using the command line.

But I'm pretty sure kainjow is right and you can't actually checkout using Xcode.

Eraserhead said:

Well terminal works. Thanks for the info guys . I'm looking forward to Leopard more now!

Click to expand...

Terminal is quite good....

1. svn co <url>
2. svn add <filename>
3. svn delete <filename>
4. svn commit -m <message>

I think this much pretty enough to do basic SVN stuff.

If you want to to compare use "svn diff" . .

ExoticFish said:

I only ever use SVN in Xcode to look at revision comments and using FileMerge. Everything else I just feel more comfortable using the command line.

But I'm pretty sure kainjow is right and you can't actually checkout using Xcode.

Click to expand...

XCode can make checkouts in 3.x.

I wouldn't use it for imports due to a bug which prevents you from importing, making directories/etc into the root of a SVN repo. I filed a bug way, way back... still haven't seen it fixed yet.

Eraserhead said:

Not with SSH+SVN which Sourceforge uses.

Apple have really ****ed up their SCM support in Xcode (though to be fair Microsoft Sourcesafe is worse).

Click to expand...

Last time I checked, it works, but I also use public key auth on my own servers, which may help. I don't think I have done much with SSH+SVN using actual passwords, but I don't see why it won't work if you specify the username/password correctly.

Eraserhead said:

Not with SSH+SVN which Sourceforge uses.

Apple have really ****ed up their SCM support in Xcode (though to be fair Microsoft Sourcesafe is worse).

Click to expand...

I'm coming into this a bit late but....what about not going with SVN at all and trying out one of the DVCS systems instead, Mercurial, Git, Bazzar etc? Personally, I'd go with Mercurial, using Bitbucket as a backup/public repository. The huge benefit is the the local copy contains the entire history and you can work as well disconnected from the central repository as you can connected.

Disclaimer: I confess I've never even attempted to use the built in SVN support in Xcode, so I don't know what benefits it offers or what you would lose if you didn't use it.