Xref: news2.mv.net comp.os.msdos.djgpp:3451 From: malcolm AT manawatu DOT gen DOT nz (Malcolm Taylor) Newsgroups: comp.os.msdos.djgpp Subject: Re: Size of executable Date: Sun, 05 May 1996 07:48:47 GMT Organization: Grafik Software Lines: 32 Message-ID: <4mhq5e$btp@news.manawatu.gen.nz> References: <4m8cd3$1kmk AT power5 DOT rz DOT uni-hohenheim DOT de> Reply-To: malcolm AT manawatu DOT gen DOT nz NNTP-Posting-Host: malcolm.manawatu.gen.nz Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp pfrisbie AT trmx3 DOT dot DOT ca DOT gov (Phil Frisbie, Jr.) wrote: >In article , u951303 AT rouen DOT daimi DOT aau DOT dk >>I know that there's got to be this stub-loader, dpmi-interfacing etc. >>but does this really take up all this space, or did I just overlook >>some switch? What are the options if you want to reduce the size of >>the output? >> >It's my understanding that all functions in libc get added weather they are >needed or not. If size is really critical, then compile your own libc with >just the functions that you need. NO! If all the libc.a functions were linked into every image each exe would equal 400+K! Only the ones neede for the particular image are loaded as per usual. There is however some functionality that can be discarded. Filename globbing is an example (ie expansion of wildcard arguments). Check the info files for the crt0 startup flags. These can be used to reduce the file size. Basicly it is always a good idea to read the FAQ and if possible to search the mail archives on http://www.delorie.com/djgpp/ ... If you haven't already got the FAQ then get faq200b.zip from where you got v2. >>I hope this question hasn't been brought up too often :) >> >Only every few weeks! I'm sure it's in the FAQ. Malcolm