Hi,

Please, could you rephrase, (say the same thing with other words): "where I found statistic of using modules in EXE"? I don't understand what you mean by it.

Regards,
Vincent.

-----Oorspronkelijk bericht-----
Van: o2
Verzonden: maandag 15 september 2003 16:15
Aan: lazarus
Onderwerp: [lazarus] small improvement of register + need statistic

�Hi
I try to recompile small program originally write for Delphi And I found not necessary unit Controls used in REGISTRY and second problem: the same program compile under : Delphi 3.0 and size of EXE is 79kB
Delphi 6.0 - EXE=144kB
FCP 1.1 + lazarus = 300kB

where I found statistic of using modules in� EXE �
Darek

I need:
Detailed map of segments
in Delphi linker generate public MAP FILE
for example fragment of *.MAP from Delphi
0001:00000000 00006C0F C=CODE S=.text G=(none) M=System ACBP=A9 0001:00006C10 00000140 C=CODE S=.text G=(none) M=SysInit ACBP=A9 0001:00006D50 000000A4 C=CODE S=.text G=(none) M=Types ACBP=A9 0001:00006DF4 00000F4C C=CODE S=.text G=(none) M=Windows ACBP=A9 0

Well. please don't use html in your e-mails unless its actually needed :)

But how did you compile your app? Static, Dynamic or smart linking? From my experiance Smart Linking can give similar sizes as Delphi(if you are willing to wait for the extra compiling time), but the interfaces add extra overhead, while Dynamic is quite a bit larger then Delphi(dependent on what is being used and linked etc) eg. on this system, my DB test app with GTK1 -

FPC Dynamic Linking 3mb

FPC Smart Linking 800kb

Delphi 4 - 500kb

but a basic app without interface -

FPC Dynamic Linking - 300kb

FPC Smart Linking - 88kb

Delphi 4 -75kb

In other words, you can get far better results with smart linking, but don't expect GUI apps to be the same size. That is part of the price for supporting multiple interfaces(win32, gtk1, gtk2, gnome, etc) the additional code to abstract interfaces, also means that the lcl cannot be optimized for every interface, while the VCL is only Win32 and thus can be quite a bit less overhead.

Once we get dynamic packages we could do the same thing theoretically and put the interfaces in there own package, and have apps link to it like any other lib, which would remove the overhead from apps themselves, and should make the numbers more consistant.

For better comparison you might compare Kylix to Delphi etc.(and include the size of the qt interface library), I think you'll finder similar size overhead.

Andrew

<FONT face="Times New Roman"
size=3>�Hi
I try to recompile
small program originally write for Delphi
And I found not
necessary unit Controls used in REGISTRY
and second problem:
the same program compile under :
Delphi
3.0 and size of EXE is 79kB
Delphi 6.0 - EXE=144kB
FCP 1.1 + lazarus = 300kB

where I found statistic of using modules in�
EXE
�
Darek

Use -k-M on the fpc commandline

Or use objdump from mingw or cygwin to print information about the object or executable.

Peter