[Lazarus] Compiled file size (again)

[Martin]

On 14/12/2011 17:34, Jürgen Hestermann wrote:
> I know this topic has been discussed multiple times but I am 
> astonished about it repeatedly.
> I know that FPC/Lazarus exe files are way larger in size than i.e. 
> Delphi exe files.
> But I am wondering why it even increases in such short time slots:
>
> I compiled my program without change with the following builts
> and resulting sizes (after stripping debug information):
>
> Lazarus-0.9.31-33059-fpc-2.5.1-20111024-win32: 1.643.520 bytes
> Lazarus-0.9.31-34078-fpc-2.5.1-20111210-win32: 1.872.896 bytes
>
> The size itself is huge IMO but it even increases rapidly.
> 229,376 bytes (nearly 14%) added in not even two months is a lot.
>
> Anybody who has an idea why?

no idea,

but some of the size is because the compiler (nor the IDE) can not know 
certain thinks.

Like what will be loaded from resources. Any published property could be 
accessed.

As soon as anything (even the forms icon, or an icon for a button) uses 
graphics, those graphics could be in any format. And more the app could 
open an image from a file that the user selects at runtime. Historically 
ass that always worked (that's how RAD works, the programmer does not 
need to think about those thinks)

So unit graphics and those used by it register all graphic decoders 
(png, jpg ...) in initialization sections => and those decoders are 
always present (can not be smart linked away)

Try finding and commenting them to see how much that is ...

find other similar code...