Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!dptg!pegasus!hansen
From: hansen@pegasus.ATT.COM (Tony L. Hansen)
Newsgroups: comp.lang.c++
Subject: Re: C++ for DOS/OS2
Summary: a small trick
Keywords: C++, Glockenspiel, DOS
Message-ID: <4109@pegasus.ATT.COM>
Date: 22 Sep 89 14:40:46 GMT
References: <661@windy.dsir.govt.nz> <1456@dinl.mmc.UUCP> <672@windy.dsir.govt.nz>
Reply-To: hansen@pegasus.ATT.COM (Tony L. Hansen)
Organization: AT&T ISL Middletown NJ USA
Lines: 25

< I haven't found this very satisfactory; I still need to use a batch file
< and avoid 'make' to do my big files. If you use this roll out mechanism
< compile times can rise amazingly - say from 100 seconds to 2000 seconds.

When I use one of the cfront ports under DOS, I found this small trick
useful. Because cfront can run out of memory so easily, even using make can
push things over the limit. So instead of running make directly to build
things, I run it indirectly via a small batch file:

mk.bat
	make -n %1 %2 %3 %4 %5 %6 %7 %8 %9 > tmp.bat
	tmp

The "make -n" will run through all of its checks and print out exactly what
it would have done to build your process, creating another batch file which
then gets run to do the actual compilation. Doing things this way permits
you to compile your programs with nothing but command.com running, yet still
being able to take full advantage of make's powers.

I hope that this can save someone somewhere some time waiting on those long
compiles!

					Tony Hansen
				att!pegasus!hansen, attmail!tony
				    hansen@pegasus.att.com