Gv,
My concern relates to using a binary built by someone else that has an
unexplainable size. I will move forward by rebuilding the source myself, so
this isn't a major issue.
It is my understanding that a debug binary includes many additional
bytes of symbol table information that the release build does not.
Therefore it's not the 132 bytes difference that I was questioning, it was
why that the release binary wasn't several hundred kilobytes smaller than
the corresponding debug build.
Jerry
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Gisle Vanem
Sent: Tuesday, November 23, 2010 11:25 PM
To: libcurl development
Subject: Re: libcurl-7.19.3-win32-ssl-msvc - release lib file is larger
thandebug?
"Jerry W. Rice" <[email protected]> wrote:
> I've downloaded the 'libcurl-7.19.3-win32-ssl-msvc' zip file, and
installed
> it on my Windows development system. I intend to link the 'libCurl'
static
> release library file (lib/Release/curllib_static.lib) with my Windows
> application. I've noticed that the pre-built Release library file is 1857
> Kb in length. On the other hand, the pre-built static Debug library file
is
> 1733 Kb in length. This seems unusual.
No so strange. All lib-files contains the (relative) path of the objects it
was
built from. I.e 'release\version.obj' vs 'debug\version.obj'. There are 65
objects
in each lib. The word 'release' is 2 letters longer than 'debug'. Hence the
release
lib is rightly 130 bytes larger. There could be other reasons, but why care?
--gv
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
