Alex Zavatone:
You can't. It's hell.
One really big problem that I have because of this is all the build folders
being created within my sub projects when I need to switch back to Unique.
Aaah, well, all I can say is that Quincy's advice worked for me. But from your
descriptions I don't think I'm doing anything nearly as complicated as you. I
was just after a one way conversion away from legacy, without a need to switch
back and forth.
The REALLY BIG PROBLEM that you have here is you run the risk of putting
your build folders into your repository when you do this and need to switch
back and forth between Legacy and Unique.
Yes, I can see that is a risk, but because on some other projects I work on I
(unfortunately) need to still run Xcode 3.2.6[1] I'm well versed in using the
various DVCS .ignore files to exclude entire build directory subtrees (and
other litter, .DS_Store I'm looking at you) so that's not a mistake I'm likely
to make. Oh, and I'm one who definitely doesn't attempt to use Xcode (or any
IDE) to do version control, even for the subset of projects for which I need
to use Git[2]. Actually, I'm fairly fanatical about keeping my repositories
clean, so I tend to be hyper-vigilant about what gets added in the first place.
[1] I admit I used to love 3.2.6 in preference to more modern Xcodes, but
3.2.6 is flaky in VMs, so it's now quite unpleasant.
[2] Yep, a Mercurial user here, so there's no risk of Xcode confusing things.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
