Re: Workspaces question.
Re: Workspaces question.
- Subject: Re: Workspaces question.
- From: Quincey Morris <email@hidden>
- Date: Fri, 06 Jun 2014 11:59:52 -0700
On Jun 6, 2014, at 10:45 , Fritz Anderson <email@hidden> wrote:
Workspaces aren’t meant to be shared
I don’t want to be dogmatic about it (in case I’m wrong) but there’s no problem sharing workspaces AFAIK. Indeed, a shared workspace is an integral part of the automatic clone mechanism that Xcode 5 introduced, IIRC.
Alex’s problem is that a workspace is expected to enclose a reasonable source hierarchy, and if the file names are ambiguous within the workspace then bad things can be expected to result. Perhaps there are some advanced Xcode things that can be done to resolve the ambiguity (header maps and preferences->source trees come to mind as features I’ve heard of but never used), but otherwise a better approach might be to resolve the file ambiguities and/or use multiple workspaces.
Unfortunately, what Xcode does to search for header files (which I suspect is the heart of Alex’s problem) is a mixture of C standard requirements, C pragmatic conventions and Xcode’s own obscure rules. It probably takes some superhuman abilities to understand all 3 and how they interact.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden