SVN and cocos2d migration...What am I missing?

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

SVN and cocos2d migration...What am I missing?

(4 posts) (3 voices)

Started 1 year ago by Questor
Latest reply from Questor

Tags:

Questor
Member

Greetings,

I am trying to upgrade my Cocos2d version to the latest. The issue is complicated by the fact that I am also using SVN (XCode client).

I have successfully tagged and backed up my repository. However, I am unsure of the steps involved in migrating to the latest cocos2d.

What I tried was to check out my project, delete the cocos2d source, and then import them (Add->Existing Files) back into the project. While this appeared to work, SVN does not acknowledge that any of the lib files were changed/replaced. I thought about deleting my lib directory on SVN and re-importing the new lib directory, but I am again unsure if this is right approach.

Also, I am left wondering if simply updating the cocos2d sources is enough or do I need to create a new project in the new version using the latest template and update it with my source files? ( I am concerned because I am not sure if the template is doing alot more stuff "behind the scenes" that may come back to haunt me if I don't use it).

Any help would be greatly appreciated,
Thanks,
Q

Posted 1 year ago #
SwizzerSweet
Member

The SVN support built into XCode is very unreliable. If you can afford it, everyone (including apple) raves about Versions.

Posted 1 year ago #
MrMojo
Member

i'd say close and restart xcode, and do a "Build | Clean All" to ensure you're building from the actual source.

Posted 1 year ago #
Questor
Member

Thanks for the replies. I got it all worked out...at least it appears to be working good now. Here is what I did if someone finds themselves in a similar position:

It seems that XCode was not giving me the whole picture as far as why it was ignoring the added lib files. However, when I went into RapidSVN, it would (correctly) denote the files as obstructed. Doing a search I found this post:
http://stackoverflow.com/questions/335980/what-causes-svn-commit-to-fail-and-report-a-file-dir-as-obstructed

It seems that with SVN you cannot do the old checkout-replace-checkin trick for files with alot of changes. Instead I had to use SVN to delete the old lib directory from the repository (using RapidSVN, and clicking recursive), and then add and commit the new lib (again recursively).

One other issue I stumbled across was that I accidentally used RapidSVN to check out code to a directory and I really wanted to check it out to a subdirectory (in that directory). As it turns out SVN would not allow me to checkout into the subdirectory because the parent was now a "working copy". Apparently the only way to get SVN to forget about the directory as a working copy is to delete the directory (or at least delete the .svn hidden directory inside the checked out directory).

Thanks again for the help and advice.
Regards,
Q

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.