On May 18, 2017, at 3:09 AM, Quincey Morris < email@hidden> wrote:
On May 17, 2017, at 18:03 , Bryce Glover < email@hidden> wrote: AFAIK, custom Xcode templates have never been officially supported, …
Well, that’s the impression I’ve gotten from the lack of documentation on the construct, but it’s still somewhat depressing to hear I’m not the only one to harbor this perspective. More’s the pity, then, I suppose, as I’ve been hoping this functionality would help me simplify my workflow. …and unofficial ones have tended to break between Xcode versions.
This doesn’t bode well, either…
…
You’re better off creating a project that’s set up the way you want, then duplicating the containing folder when you want a new “template”. Note that if you rename the project from within Xcode, you’ll get a dialog that helps you to rename the various things (file names, module names, executable names, etc) that inherit the project name. In general, you should avoid renaming the project file in the Finder. (It ought not to matter, but we’ve seen reports of projects getting broken after doing that. This may be due to some absolute path names inside the project, or something less scrutable.)
That’s a bit of a kludgy workaround, but I suppose it may end up having to do for now despite my lack of enthusiasm for and satisfaction with it if nothing else comes up to turn things around. The fact that, as you’ve just described, Xcode apparently doesn’t like to propagate filesystem state does strike me as strange, too, though…
|