Why is it so hard to copy an Xcode project?
And this isn't just XCode, I have had the same trouble in VisualC.
Is there any way to copy a project that does not involve mucking with the individual files/
And this isn't just XCode, I have had the same trouble in VisualC.
Is there any way to copy a project that does not involve mucking with the individual files/
Never had any problems copying Xcode projects myself. Just copy the top level directory (the one the .xcodeproj file resides in). I've used this to move projects between directories on the same machine as well as copying the project to a new machine.
If you run a clean before doing the copy you'll cut down on the cruff that resides in the project, you'll copy a smaller amount of data and the build in the new location will go easier.
Never used VisualC so can;t comment on that.
Yes, but then you have to go through this:
https://developer.apple.com/library/ios/qa/qa1625/_index.html
to rename things.
I guess I'm missing your point. You asked about copying a project as I wrote I've never had a problem doing it as I outlined.
As for renaming a project that's a different situation as I am sure you realize. And even at that looking at the link you posted the procedure does not seem overly onerous.
And of course there is no need to rename if you are moving or copying a project,
regards
Maybe copy is the wrong word, I would like to fork a project, rename it and continue with both projects.
Keith Barkley wrote:
Yes, but then you have to go through this:
https://developer.apple.com/library/ios/qa/qa1625/_index.html
to rename things.
I think you didn't see the note on that page that said:
Note: Retired Document
This document has been retired.
This page will be removed in the future. Please update any bookmarks.
I renamed a project the other day in Xcode6.1 without too much effort. Just change the name of the project inside Xcode. Xcode will handle the rest. The only thing it left were a couple of comments and the name of the containing folder. Even there, that was only a couple of places like the InfoPlist file.
Keith Barkley wrote:
Maybe copy is the wrong word, I would like to fork a project, rename it and continue with both projects.
Yep I agree, copy is definitely the wrong word 😀
If you are looking to fork a project I suggest you use the source code control tools in Xcode. Will make managing both forks a lot easier.
Thanks, guys. Maybe I am making too much of this. In VisualX it is hard because there is a wierd mix of absolute and relative paths which don't survive a simple copy/rename of the folder. I saw several complicated procedures on the net, but I guess things have improved.
Why is it so hard to copy an Xcode project?