Oh! Apple

My experience of using iPod Touch, iPod Classics, Mac OSX, Coding in XCode, or anything generally related to Apple

Wednesday, August 01, 2012

Forcing myself to develop for OSX

I was trying to create an environment which, whenever I feel like doing development in whatever platform (WPF, Android native, HTML5, Windows 8 Metro, MacOSX, iOS ...), I can do that at ease, have everything backup, version controlled and unit tested.  I pretty got the Microsoft dev and Android dev environment working.  Now I need to figure how how to do that with Mac OSX.

The first hichup I encountered was that Eclipse on MacOSX didn't work well with the Subversion server I set up on my server box.  I tried hours and finally gave up.  I got messages like "a known bug" or "Mountain Lion removed some critical subversion access required files ...".  The bottomline is that I don't have time to fight with the environment.  I only wanted to causally write some MacOSX stuff with XCode once in a while.  I have no time to fight with this bullshit.

And then I found that XCode subversion didn't work too.  Again, hours of fighting, lots of fustration.  Not worth the time.

Finally I found out that the best way to do it is by using self-contained, git support that comes with latest XCode 4.x.  That way, all I need to do is back up the whole folder of the project, and I have both the project and version control backed up.  So my final test is to if it's possible to have the Mac OSX project resides on the network server instead of the local file system.  Otherwise I need to set up some file sync mechanism to make sure that everything got backup properly.




0 Comments:

Post a Comment

<< Home