EXE grows very large

rbuser

Hello all:

I have very strange experience. I am doing many change in Report
Builder reports but only have maybe 5 reports. The exe file should
only be maybe 1.3 - 1.5 MB. Now, it jump to 3.9MB and sometimes go
back 1.4 MB. I don't know what causing this, I only have Report
Builder as 3rd party package. Running Delphi Prof 6.0. I was hoping
to get lucky compile to go back to 1.4 but no luck. yes, i rebooted
and everyting. Just started doing tonight. I was experimenting header
detail type reports.

Since I'm new in report builder i can safe to say these are pretty
simple report.

any suggestion?

rbuser

You won't back to 1.4 Mb
RB VCL is big and now is included in your code (no matter how much reports
your application have, just as the Delphi VCL included for just one form
is the same than for n).
So if you want to decrease the exe size you must use runtime packages
(which only reduces your exe size, not the total deployment one).

digitalmetaphors

There's no such thing as a luck compile The exe must have blown up for a
reason. Check your uses clause for units you don't need or components on the
form that you aren't using but forgot to remove. If you want to minimize the
size of the exe then try building with packages.

--
Cheers,

Alexander Kramnik
Digital Metaphors

rbuser

Normally i am developing with VisualBasic and the first i saw was,
that Delphi-Apps are very big - so i searched for a solution.
Now i use UPX - it's a free executablepacker and reduces the size to
only 15 to 40 percent of the original size!
It's really great.
Search after UPX in google
... and excuse my bad english :-)

Daniel

rbuser

> Normally i am developing with VisualBasic and the first i saw was,

Visual Basic applications are even bigger, the .exe file can be smaller but
it needs to install a lot of aditional dll, ocs, and so on. If you want a
small Delphi exe file, compile with run-time packages.
The disadvantage is that you'll need to deploy a lot of files besides a
single .exe.


Yes, but the program is decompressed when loaded into RAM. Works for
distribution but has no effect at runtime.

--
Guillermo Castaño Acevedo
Gerente de Sistemas - Grupo Millennium Ltda
GuillermoC@GrupoMillennium.com
http://www.GrupoMillennium.com

rbuser

Hi Guillermo,


Unfortunately it has effects at runtime, the whole application gets loaded
into memory and can't be optimized by the OS's memory management.

regards,
Chris Ueberall;