🚀 go-pugleaf

exuhag@exu.ericsson.se (James Hague) writes:

> The downside to Borland MAKE, as has already been mentioned, is
> that the documentation really stinks.

Now that you mention it.....

I've got a library in progress, and I'm adding modules occasionally.
Since each module has to be tested before addition, the .obj is
natuarally not out of date against its .c file.

So... how do I write rules that specify the .lib depend on the component
.obj's and force the recompilation of said .c files and their
addition/update into the lib?  (they need to be recompiled to remove the
main() that lies inside an #ifdef TEST)  The Borland MAKE documentation
says nothing helpful.  In fact, I can't seem to find anything at all
that would help here.  Default rules fail, because the name of the .c
file differs from the name of the .lib.  I don't particulary want to
have to write a unique rule for each and every module.
--
Due to failure of my mail connection, please use the following emergency
                          addresses to reply:
roy%cybrspc@tfsquad.mn.org   cybrspc!roy@tfsquad.mn.org   roy@tfsquad.mn.org