Xref: news2.mv.net comp.os.msdos.djgpp:7207
From: spiner AT comp DOT vuw DOT ac DOT nz (Steve Piner)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP's .exe's are TOO large
Date: 13 Aug 1996 10:22:40 GMT
Organization: Dept. of Comp. Sci., Victoria Uni. of Wellington, New Zealand.
Lines: 27
Message-ID: <4upl1g$r23@wnnews1.netlink.net.nz>
References: <4uk6qr$795 AT utdallas DOT edu> <Pine DOT NEB DOT 3 DOT 95 DOT 960812142450 DOT 16040A-100000 AT ananke DOT amu DOT edu DOT pl>
NNTP-Posting-Host: depot.comp.vuw.ac.nz
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <Pine DOT NEB DOT 3 DOT 95 DOT 960812142450 DOT 16040A-100000 AT ananke DOT amu DOT edu DOT pl>,
Mark Habersack  <grendel AT ananke DOT amu DOT edu DOT pl> wrote:
: On 11 Aug 1996 lafitte AT utdallas DOT edu wrote:
: 
: >     The program :
: >main() {
: >
: >}
: >compiles to something like 30 or 40k!  What gives. 
....[Stuff about startup code snipped]
: If you're making little apps then better stick to real mode and TC++ or
: something similar. If you really want to create small 32-bit apps and the
: executables are too big for you - get djp, it will save about 60% of the
: space occupied by an unpacked executable.

Another little trick is to strip your Coff files.  Gcc adds some
rudimentary debug info even when compiling without the '-g' option.
If you compile to Coff - 'gcc -o foo ...' - rather than exe - 
'gcc -o foo.exe ...' - then you can strip the resulting binary and use
stubify to turn it into a much smaller exe.

Steve
-- 
 ____ ____
/ __//___ \  Steve Piner - spiner AT comp DOT vuw DOT ac DOT nz
\__ \ |  _/-----------------------------------------------------
/___/ |_|    (yes, I know it's a BUAF, but it's *my* BUAF) :-)