Path: utzoo!utgpu!watserv1!watmath!att!rutgers!apple!agate!shelby!portia.stanford.edu!dhinds
From: dhinds@portia.Stanford.EDU (David Hinds)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Compiling GNUPLOT with Topspeed C - Got it!
Message-ID: <1990Jul21.040453.27200@portia.Stanford.EDU>
Date: 21 Jul 90 04:04:53 GMT
References: <1990Jul18.171005.8884@portia.Stanford.EDU> <2005@cod.NOSC.MIL> <9951@pt.cs.cmu.edu>
Organization: AIR, Stanford University
Lines: 22

In article <9951@pt.cs.cmu.edu> ralf@b.gp.cs.cmu.edu (Ralf Brown) writes:
>In article <2005@cod.NOSC.MIL> ganzer@cod.nosc.mil.UUCP (Mark T. Ganzer) writes:
>}Did you use the same drivers that were used in the Turbo-C makefile? The
>}version I downloaded from SIMTEL has an executable size of 204K and was
>}compiled with Turbo-C, but has a smaller set of output drivers.

    When I compile with the PC, HERCULES, CORONA, EPSON, POSTSCRIPT, HPGL,
HP75, ATT6300, and DXY800A drivers (all the ones in the TC makefile), the
resulting executable is 151185 bytes.  If I compile with only the PC and
POSTSCRIPT drivers, and turn on 80386 code generation, I get 144581 bytes.

>Also, compiling with debugger info generally comes pretty close to doubling
>the size of the executable.

    I think the 296K TC figure is with debugging information; the 204K, I
assume, is with debugging turned off.

    Oh - someone else asked if REPLOT works.  It seems to work fine with
my executable.

 -David Hinds
  dhinds@popserver.stanford.edu