Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!gatech!uflorida!reef.cis.ufl.edu!jdb
From: jdb@reef.cis.ufl.edu (Brian K. W. Hook)
Newsgroups: comp.os.msdos.programmer
Subject: Turbo C++
Message-ID: <25970@uflorida.cis.ufl.EDU>
Date: 17 Dec 90 17:21:47 GMT
Sender: news@uflorida.cis.ufl.EDU
Distribution: usa
Organization: UF CIS Dept.
Lines: 21

I am using Turbo C++ 1.00 for my current development.  However, I have an
excessively large project file (about 26 files, 55K of source) and when
I change a single #include that is included by ALL files it will do a 
build all to keep everything consistent.  The question is:

Common sense lends one to believe that using TCC would be MUCH faster than
recompiling within the environment.  If that is the case, is there a way
to use my .PRJ file as a response file?  I've tried @FILE.PRJ on a whim,
and, of course, it didn't work.  The only way I can think of is to go into
my options windows and write everything down then make a batch file.
This is not my idea of fun, especially since a lot of things are already 
going to be defined in my .TC file and .CFG file.  And of course, certain
things that it assumes are set are not explicity displayed in the options
windows and thus I do not know what switches to set....also, certain thigs
set in the .TC file are overridden by my .PRJ file and thus at the command
line, certain .TC switches may be used instead of ones in my .PRJ file.

THIS GETS VERY CONFUSING AND ANNOYINGH!!  ARGH!  Anyone know how to handle
this in a sane manner?  Thanks....

Brian