Mail Archives: djgpp/1997/08/14/10:42:25
On Thu, 14 Aug 1997, Eli Zaretskii wrote:
>
> On Wed, 13 Aug 1997, Peter Berdeklis wrote:
> > I'm becoming "afraid" to include some of the big C++ files because the
> > compilation times increase so much. No comparison compiling with stdio.h
> > rather than iostream.h, not to mention the big STL template headers.
> >
> > This isn't really a problem on GCC since I'm running it on a mainframe,
> > but testing/debugging my code under DJGPP sometimes makes for very long
> > compile times. Including a 800 line header in a 120 line code file is a
> > pain.
>
> I don't understand. Are you telling that your DJGPP installation is
> on a slow machine? What CPU do you have there? Perhaps the slow
> compilation is due to sub-optimal system configuration. Please
> consider reading sections 3.9 and 7.1 of the DJGPP FAQ list (available
> as v2/faq210b.zip from the same place you get DJGPP).
>
Yes, I'm running DJGPP on a slow machine, by today's standards. One is a
486-33, one is a 486-100, both with 8M RAM. Although I'm sure that the
machines are not configured optimally, the problem is the big C++ header
files. I've created C only programs and C++ programs with no big header
files and the compilation time is reasonable.
Right now I'm using the machines to debug programs that I run on an SGI
machine - portable programming made very easy (thank you DJ). The GCC
installed on the SGI doesn't have debugging libraries so the -g doesn't
work. Also there's no gdb on the machine, and I hate dbx. (I know I
could download it and compile it myself, but what's the point when
there are no debugging libraries anyway.) So I test the programs under
DJGPP and when they're ready, with only a couple of #ifdef MSDOS 's
around, I hop over to the SGI, re-compile, and let them process the BIG
files. Very handy.
I'll suffer for now, but it would be great to only have to compile
iostream.h once.
---------------
Peter Berdeklis
Dept. of Physics, Univ. of Toronto
- Raw text -