Re: Setting the deployment location
Re: Setting the deployment location
- Subject: Re: Setting the deployment location
- From: Marc Poirier <email@hidden>
- Date: Sun, 1 Feb 2004 12:37:01 -0600 (CST)
On Mon, 26 Jan 2004 Scott Tooker wrote:
> The idea is that by default, when "installing" a build that the
> products go into a separate location where you can verify the contents
> before dittoing or copying the result into place (since a bad framework
> could seriously hose your system). Another benefit of installing into a
> separate location is this gives you a sparse root that can be turned
> into a package for distribution.
>
> By default this separate location is set to be /tmp (the build setting
> that controls this is $DSTROOT). Currently there is no UI for $DSTROOT.
> Although we don't recommend it, you can set DSTROOT to "/" to have
> things install in place.
I've said this before, but I'll say it again: I strongly disagree.
/tmp is a terrible default for $DSTROOT, and it should not be "not
recommended" to change $DSTROOT to /, which is a way saner value for the
VAST MAJORITY of development out there. I know that in-house at Apple,
you are doing a lot of system framework and extension development, but the
rest of the world is not! So maybe /tmp makes good sense as a default
within Apple HQ, but so far as Xcode for the rest of the world goes, it's
a crummy idea. This is a perenial source of confusion and WTFing.
Marc
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.