On Wed, 8 Jan 1997 13:28:56 -0800 (PST)  Curt Sampson wrote:

> Yes, unforuntately. After some enlightening chats with cgd, I'm
> kicking around ideas for changing the build process to fix this
> sort of thing. I'd like to have the entire system build into an
> object tree, using only the makefiles, includes, libs, etc. out of
> that object tree, so that you never have to do a `make install' of
> any kind until the very end. That way you could also do a `make
> build' without root privileges.
> 
> Currently, I'm thinking the Proper Solution involves getting rid
> of the ability to have an object tree intermixed in with the source
> tree (i.e., forcing a separate obj hierarchy with symlinks in the
> source tree). While we're at it, we might as well get rid of intermixed
> architecture object trees. In other words, for source directory
> 
> 	/usr/src/usr.sbin/config
> 
> We will have object files go in to
> 
> 	/usr/obj.sparc/usr.sbin/config
> 
> We will *not* be allowed to use (any longer)
> 
> 	/usr/src/usr.sbin/config/obj
> 	/usr/src/usr.sbin/config/obj.sparc
> 	/usr/obj/usr.sbin/config.sparc
> 
> I don't know what people think of this. I don't see this as any
> loss myself.

I would hate for the standard make config files (in /usr/share/mk) to
totally lose the ability to build into obj dirs in the source tree.
We're using the new BSD style makefiles and obj-dirs for all of our
work projects on Solaris and Ultrix boxes, and this scenario would be a
loss for us.  If the completely seperate object tree were conditinal on
whether the source being compiled was in BSDSRCDIR, this would be ok.

Simon.
--
Simon Burge						simonb@telstra.com.au
UNIX Support, CPR Project.				+61 3 9634 3974 (Phone)
Telstra Corporation, Melbourne, Australia.		+61 3 9670 1189 (Fax)