Re: Library Location
Re: Library Location
- Subject: Re: Library Location
- From: Richard Charles <email@hidden>
- Date: Mon, 13 Mar 2017 17:17:03 -0600
Sorry for the confusion, the prior back and forth email ended up in Cocoa Dev by mistake. This one is back in Xcode Users.
> On Mar 13, 2017, at 3:04 PM, Quincey Morris <email@hidden> wrote:
>
> On Mar 13, 2017, at 13:47 , Richard Charles <email@hidden> wrote:
>>
>> The location for Xcode project-generated files is specified in the Locations preference. In this preference "Derived Data:" has a Default value which is ~/Library/Developer/Xcode/DerivedData. Inside this directory is the following directory structure.
>>
>> ~/Library/Developer/Xcode/DerivedData/Build/Products/Debug
>> ~/Library/Developer/Xcode/DerivedData/Build/Products/Release
>>
>> The final build products for all Xcode projects are located directly inside these folders. They are not put in subdirectories by project.
>
> No, this is not the default preference, although you may have changed it in your Xcode installation. If you click the “Advanced” button, you will a number of sub-options, the first of which (“Unique”) is the factory default. You may have changed this to “Custom”, and thereby forced all project output into the same place.
You are right, I do remember changing this a long time ago. After clicking the Advanced button I chose the second option which is “Shared Folder” and has a default of “Build”. As I upgraded Xcode over time this modified preference persisted until I simply forgot about it.
Here is what the Xcode documentation says on the subject.
"Shared Folder: A shared folder within the derived data folder. You specify the name of this subfolder, which is shared by all projects. This choice assumes that the derived data location is not workspace-relative. This option can be used to let separate projects build into the same location so that they can share their build products. Build products are automatically shared among all projects in a workspace, so this setting is unnecessary if you can place your projects in the same workspace."
With my project a workspace quickly proved unproductive. So using “Shared Folder:” brings the benefit of sharing build products among multiple projects but without being bound by workspace features which may prove unproductive.
> Also, this is the preference for *new* projects. There is also a per-workspace (or “per-project”, if workspaces are hidden) setting on File -> Workspace/Project Settings. If you look there, you’ll see a number of choices, the default one being “Default Location”, meaning what’s in preferences, and if you click the “Advanced” button you’ll all of the same advanced settings, plus the explicit option to use preferences, which is (again) the default.
I never noticed that setting. Thanks for point that out.
> It is, I would say, very unusual and undesirable to dump all project output into the same directories. If I look in my DerivedData folder, I definitely have per-workspace/project subdirectories with long, unique names.
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. I would not be surprised if some teams at Apple are using this option.
--Richard Charles
_______________________________________________
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