Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!mips!apple!sun-barr!newstop!texsun!texbell!nuchat!moray!urchin!p6.f506.n106.z1.fidonet.org!Bob.Stout
From: Bob.Stout@p6.f506.n106.z1.fidonet.org (Bob Stout)
Newsgroups: comp.lang.c
Subject: Re: DOS make (Was: MSC 5.1 make)
Message-ID: <7139.25959362@urchin.fidonet.org>
Date: 24 Dec 89 00:17:19 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/506.6 - Fulcrum's Edge, Spring TX
Lines: 17

In an article of <21 Dec 89 18:33:45 GMT>, (Joe Keenan) writes:

 >I've had great success with one called NDMake.  Look for NDMAKE45.arc in 
 >your favorite BBS's programming utilities section.

The previously recommended Opus Make (commercial) is a much enhanced direct  
decendant of NDMAKE. Aside from additional bells and whistles, Opus offers  
much lower memory usage during execution than most other makes. It's the  
memory usage issue that's the real Achilles heel of some of the more capable  
bundled makes such as the new Microsoft NMAKE or Borland's MAKE. I often do  
fairly massive recompilation of libraries driving the various bundled MAKEs  
from simple batch files and the only one that's proven to be both capable and  
frugal with RAM has been Zortech's. Both NMAKE and Borland's MAKE tend to blow  
up partway through with various out of memory errors. NDMAKE is also OK, but  
it's hard to imagine large enough sources or cramped enough RAM to choke Opus  
Make. BTW, Lugaru also publishes a similarly frugal and generally excellent  
make that you should also check out.