On May 18, 2017, at 16:37 , Bryce Glover <email@hidden> wrote:
So I’d have to store my base project — what I would like to store as a template, that is — somewhere completely different from where I would want my derived projects to end up.
What we (or at least I) think of as a “project” is a folder that contains the .xcodeproj package (the actual project), along with the root .git repository, plus whatever directories and files get put at that level. This project folder can be renamed or moved anywhere in storage without disturbing anything going on inside it. As a direct consequence, a duplicate of this folder is also a well-formed and well-behaved project folder.
So you should store the base project folder somewhere, then just duplicate it when you want a new one. You don’t even need to rename anything inside the folder, if the project is just an exercise (which is what I think you said originally). Or, you can open the project in Xcode and go through the initial renaming process.
It’s not even really necessary to have the base project itself be under source control. It’s pretty easy now to make a repository for an existing project, from within Xcode. The only thing you really need to do is to fix the .gitignore file before you commit anything, since Xcode’s standard one is inadequate. |