On 1/30/07, Thomas Hruska <[EMAIL PROTECTED]> wrote:
> > Why does CygWin produce such a large C++ binaries?
>
> Brett, have you taken the EXE apart? Any number of things could be
> happening: Static linking, massive (and unnecessary) string and numeric
> mapping tables getting compiled in and not removed even though the
> functions using those tables are never used, symbol table inclusion,
> etc. You'd have to analyze the file with PE tools (tools that take
> apart PE files) to figure out what's being included that is causing the
> size difference. Also, PE files are probably naturally larger than the
> ELF equivalent (you can store a lot of junk in an EXE such as bitmap
> resources).
No, I didn't look at the .exe yet... I will post if I find anything.
It's possible that there are options CygWin uses by default that don't
apply to the Linux version of gcc (linking Windows runtime stuff?). I
don't normally use CygWin anyway, I just wanted to see how it compared
with the Linux equivalent.
I'd like to see a similar comparison done with MSVC++ -- just a
straight command-line compile, like one would do for gcc.
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
