On Mar 13, 2017, at 16:17 , Richard Charles <email@hidden> wrote:
Well perhaps it is unusual, but Apple has placed the “Shared Folder” with a default of “Build” as the second choice when clicking the Advanced button so somebody must be using it.
(Sorry, I didn’t notice the jump between lists, either.)
Well, it’s clear now why your current solution/workaround works.
In regard to the desirability of using shared folders, I think I’d put it this way: I have no problem with a specific workflow that leverages a shared build folder between (say) project A and project B like you have. However, in that case, I think it would be better to achieve that by using the File -> Project Settings dialogs in the two projects, rather than changing your Xcode preferences.
If nothing else, by changing the settings globally, you risk file name clashes in future, when building different projects that happen to re-use the same names for sub-components that come from different source code. Let’s say you duplicated your library project to make a version with additional logging, that you might occasionally use to debug intractable bugs. Your two library projects would then interfere with each other, unless you were very certain to rename everything (targets, modules, etc) that affects build directory file names. You risk very hard-to-find bugs as a result of using un-recompiled files.
|