>Date: Mon, 25 Nov 1996 15:07:59 -0500
>From: Chris G Demetriou <Chris_G_Demetriou@ux2.sp.cs.cmu.edu>

> The notion would be that you could say:
>"make" at the top, which would translate into "make all" which would
>in turn translate into "make all-install all-lib all-bin all-share"
>etc., and you should be able to restrict which targets each of the
>generic targets (all, install, clean, etc.) expands into.

>e.g. 'isntall-includes' is 'make includes'...  but 'make install'
>doesn't install the include files, etc.

Whatever solution you create, just be careful how it slices up the
tree.  The way 'make includes' is implemented now is somewhat silly,
in that for 99% of the directories in the tree (i.e. everything but
src/include, src/domestic/include, src/sys, and src/usr.bin/lex) it
does nothing.  So if you 'cd /usr/src; make includes' it takes a LOT
longer than if you break it down and run 'make includes' in each
directory that installs headers.  There must be a way to prune
the tree for such a sparse target.
-- 
Mike Long <mike.long@analog.com>     <URL:http://www.shore.net/~mikel>
VLSI Design Engineer         finger mikel@shore.net for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA       (eq (opinion 'ADI) (opinion 'mike)) -> nil