🚀 go-pugleaf

->From daemon@interviews.Stanford.EDU Tue Apr  7 19:44:21 1992
->Received: by interviews.Stanford.EDU (5.57/Ultrix3.0-C)
->	id AA21432; Tue, 7 Apr 92 04:43:27 PDT
->Received: by interviews.Stanford.EDU (5.57/Ultrix3.0-C)
->	id AA20700; Tue, 7 Apr 92 04:23:55 PDT
->Received: by lurch.Stanford.EDU (5.57/Ultrix2.4-C)
->	id AA03489; Tue, 7 Apr 92 04:22:13 PDT
->Received: by shelby.Stanford.EDU (5.57/Ultrix3.0-C)
->	id AA03748; Tue, 7 Apr 92 04:21:16 -0700
->Date: 7 Apr 92 09:39:35 GMT
->From: G.Joly@cs.ucl.ac.uk (Gordon Joly)
->Subject: ivmkmf template macro for "MakeObjectOnly".
->Message-Id: <2459@ucl-cs.uucp>
->Sender: owner-comp-windows-interviews@shelby.stanford.edu
->To: comp-windows-interviews@shelby.stanford.edu
->Status: RO
->
->
->Is there a macro to make objects files only (*.o files), that is to
->say *not* to build a library or an a.out?
->
->____
->
->Gordon Joly                                       +44 71 387 7050 ext 3703
->Internet: G.Joly@cs.ucl.ac.uk        UUCP: ...!{uunet,uknet}!ucl-cs!G.Joly
->Computer Science, University College London, Gower Street, LONDON WC1E 6BT
->
We're interested to know too. Our situation is that we have several
source code directories. Some directories are InterViews-related while
others are not. We want the ability to select different combinations of
object files from a pool of object files so that different executables
can be eventually formed. "ivmkmf", without "MakeObjectOnly" option,
forces us to maintain our own version of makefiles.

leo@hkueee.hku.hk
Leo Chow
EEE Department
University of Hong Kong