Message-ID: <38D18FEC.47761548@caresystems.com.au>
Date: Fri, 17 Mar 2000 11:52:44 +1000
From: leon <Leon AT caresystems DOT com DOT au>
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: precompiled headers and djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000316171900 DOT 5735E-100000 AT is> <38D161B5 DOT C1AFAE1B AT caresystems DOT com DOT au> <tts2dsgm6qhqsc01eoullfn5usvkbbple0 AT 4ax DOT com> <200003170054 DOT TAA09047 AT envy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

DJ Delorie wrote:
> 
> > It's not DJGPP.  It's GCC (and cc1*.exe) that compiles your code.
> > DJGPP, technically speaking, is a C library and a set of tools to make
> > GCC work with DOS, right?
> 
> DJGPP is what you get when you put all the pieces together to get a
> complete development environment for DOS.

ok - but what i mean is - since percompiled headers are the issue in
windows env and not in dos and YET one can use djgpp + software add on
library (forget its name) to code for win32 then what is the part that
is in control of deciding whether or not to support precompiled
headers?!

in other words is it the responsibility of compiler to support
percompiled headers and if so then i presume some another compiler (from
a library add on for win32) is used to compile the code.

In other words - it is cool if djgpp does not support precompiled
headers - but if it IS used in coding for win32 (as is the case) then
the issue of precompiled headers is surfaced again? or would it be up to
the software add on (which supports win32 compilation) to suport
precompiled headers?