🚀 go-pugleaf

According to page 111 of _Managing Projects with make_,
Dec. '91 printing:  

"For a tool that is so widely distributed,
imake remains extraordinarily underdocumented."


"imake" is a program which reads an "Imake.tmpl"
file in a specified directory, and writes a Makefile.


Example 0.1 about imake:

The Imakefile contains:

target1 : prerequisite1
	action1

The Imake.tmpl file contains:

#include "./Imakefile"


Example 0.2 about imake:

The Imakefile contains:

f_to_o(prog1)

The Imake.rules file contains:

#define f_to_o(fileNameStem) @@\      [the backslash is last char. on line.]
fileNameStem.o : fileNameStem.f @@\ 
	$(F77) $(FFLAGS) -c fileNameStem.f @@

The Imake.tmpl file contains:

#include <Imake.rules>
#include "./Imakefile"


In all examples, any Imake.tmpl file, and any Imake.rules file,
is in a directory which will be specified in the -I option of
the imake command; and the Imakefile is in the current directory.

Given the files of example 0.1 or of example 0.2, one runs imake
with the following command:

imake -I/full_path_name_of_the_directory_containing_Imake.tmpl

and it generates a Makefile in the current directory.

Why one might want to use imake:  The Imakefile is typically
much shorter and easier to read than the corresponding Makefile.

The rules in Imake.rules are (multi-line) cpp macros.


--------------

There.  I hope someone takes an interest, even if only
to point out a mistake.  "0 articles" in alt.uu.comp.misc
my foot!  Now at least there is 1 article in here.

lehman@ames.arc.nasa.gov