Re: /Library/Caches/com.apple.Xcode.<UID> is huge!
Re: /Library/Caches/com.apple.Xcode.<UID> is huge!
- Subject: Re: /Library/Caches/com.apple.Xcode.<UID> is huge!
- From: Chris Espinosa <email@hidden>
- Date: Fri, 25 Nov 2005 13:10:10 -0800
On Nov 25, 2005, at 11:57 AM, Bertrand Landry-Hetu wrote:
2005/11/25, Chris Espinosa <email@hidden>:
On Nov 25, 2005, at 2:50 AM, Matt Gough wrote:
On 24 Nov 2005, at 20:21, Scott Tooker wrote:
Actually the default is 1024MB (1GB) :)
Another interesting default to look at if you are low on disk space
is BuildSystemCacheMinimumRemovalAgeInHours.
Equally interesting is why it puts it in /Library/Caches in the first
place. Having set up a custom Build location in the Xcode prefs,
shouldn't they go in there instead?
If you have two projects that have separate build directories, but
share a prefix file, they couldn't share the precompiled headers if
they were in separate build directories. Hence the common location.
Was there a reason why ~/Library/Caches was not used instead? Having
one folder per user in /Library/Caches seems against the idea of
/Library/Caches.
Because we use this feature internally at Apple, and in our production
build environment, the home directory of the build machine is not
writeable. As may be the case in other headless build farms.
Chris
_______________________________________________
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