🚀 go-pugleaf

I should also point out that while on the surface this looks like a
pain, in actuality it's not that bad for a couple of reasons:

 1) You can put the rules in a "global makefile" that gets included by
    GNU make's "include" feature; this means all you need to put into
    the individual makefiles is the values for PUBHDRS, PUBBINS, and
    PUBLIBS.

 2) In the future you may well want to do something different with the
    different types of files; this makes that simple.  For example, to
    save rebuild time I recently instituted a special version on install
    for headers only which doesn't copy them up if they haven't
    changed.  And you can ranlib libraries, etc.

However, I won't go so far as to say I don't miss the $$@ functionality
at all (although I _really_ dislike the format--using the $$).
-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@baynetworks.com>         Network Management Development
 Senior Software Engineer                                   Bay Networks, Inc.
-----------------------------------------------==<http://www.baynetworks.com/>-
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
     These are my opinions--Bay Networks takes no responsibility for them.