Re: Setting the deployment location
Re: Setting the deployment location
- Subject: Re: Setting the deployment location
- From: James Duncan Davidson <email@hidden>
- Date: Mon, 26 Jan 2004 17:59:16 -0800
On Jan 26, 2004, at 15:47, 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.
Right. But for the most part, people aren't developing frameworks, they
are developing applications that won't have such a detrimental effect.
But that's not the real problem with this strategy...
By default this separate location is set to be /tmp (the build setting
that controls this is $DSTROOT).
And this is the real problem. $DSTROOT builds out to /tmp which is
invisible except on the command line. If $DSTROOT was something else
that was visible in the finder, or even was in a "dist" directory that
was parallel to the build directory location, it would be much more
obvious what was going on.
Currently there is no UI for $DSTROOT.
Although we don't recommend it, you can set DSTROOT to "/" to have
things install in place.
Personally, I agree with not setting it to /. But I probably will be
experimenting with setting $DSTROOT=$BUILD_ROOT/../dist or some
equivalent that doesn't have the ".." in it.
_______________________________________________
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.