cvs.gedasymbols.org/archives/browse.cgi | search |
From: | "Michal Strelec" <strelec AT adam DOT osu DOT cz> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Super-huge EXE files |
Date: | Tue, 31 Aug 1999 13:52:53 +0200 |
Organization: | Czech Technical University |
Lines: | 20 |
Message-ID: | <7qgfnm$2sf3$1@ns.felk.cvut.cz> |
References: | <MPG DOT 1233e01be3a3061898983b AT news> |
NNTP-Posting-Host: | cl106161.osu.cz |
X-Newsreader: | Microsoft Outlook Express 4.72.3155.0 |
X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.3155.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
What is small size of program? I compile much more smaller program in DjGpp then always compared BC3.1. But it depand on use. This extra small hello examples has no real use. For example I have program which has big amount of global data and BC is almost unusable. I have to compile in huge memory model and in some cases even THIS doesn't work. So I can't compile my project in BC. It's all fault of BC's disability of compiling files bigger then 200kB. But DjGpp has NO problems. And compare my results. DjGpp> final exe has 111kB Bc3.1> final exe has 260kB. And the debuger in BC in this large files has VERY strange manners. And MAKE (in borland) it's ABSOLUTLY unusable. It has limit of 127 char as parameter. So if you have to link several libraries (whitch has long path), you're out. So I want thanks all the people for programming DjGpp. Mike
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |