🚀 go-pugleaf

We have a set of programs (C and C/SQL) being worked on by multiple
programmers. Usually each program has a "main()" source file and
several support modules with header files. These support modules are
shared accross most of the programs.

All the source is stored on a common area and access is controlled 
via RCS. I am trying to set up a common makefile that will:

- checkout any files that are needed to satisfy the make.
- pre-compile the C/SQL files.
- compile the C files
- link the program.

What rule should I use to check out a file? At present I use 
.DEFAULT:
	co ...
It seems bad to use .DEFAULT in this way.

What is the prefered method of pre-compiling/compiling. Bear in mind that
it needs to be specified implicitly because of the large number of
programs, and not all programs are to be precompiled.

Each program has a target with all its dependant object files listed.
Each object file    "    "     "    "    "    "  source   "     "   .

Do I need another target for C/SQL files? I am curious to see other
attempts at handling this. If you have a makefile that does all this
I'd like to see it. In particular the pre-compile type stuff.

What I have does work, but it does not retrieve the latest file from RCS.
Also it would be nice if it could clean up all the pre-compiled code
if compilation was successful.

Any help muchly appreciated.
--
D.T - ccdavid@uqvax.cc.uq.oz.au