-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/13/2011 10:56 AM, Jan Hudec wrote:
> In my experience, the .o files are significantly larger than the resulting
> binary.

The size command will tell you how big the code (aka text), data and zero
initialized data (aka bss) are for object or shared library files.  Anything
beyond those is the gunk you mentioned (symbols, linker information,
comments from various tools, debug info etc).

Here is the amalgamation compiled for Linux 32 bits as both an object file
and as a shared library.  No SQLite -D flags given and -O2 used, but not -g.

$ ls -lh sqlite3.so sqlite3.o
  506K  sqlite3.o
  521K  sqlite3.so
$ size sqlite3.so sqlite3.o
   text    data     bss     dec     hex filename
 481211    6608    1164  488983   77617 sqlite3.so
 433729    3224    1132  438085   6af45 sqlite3.o
$ strip sqlite3.{so,o}
$ size sqlite3.so sqlite3.o
   text    data     bss     dec     hex filename
 481211    6608    1164  488983   77617 sqlite3.so
 433729    3224    1132  438085   6af45 sqlite3.o
$ ls -lh sqlite3.so sqlite3.o
  428K  sqlite3.o
  482K  sqlite3.so

If you are trying to monitor size then use the size command!

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4eIKsACgkQmOOfHg372QRZ+wCgscuRxOlwfQpYuHRLAqEVKfpf
mswAn2XMpVFPcmn2nJop0WpPCYguQy1K
=AHFo
-----END PGP SIGNATURE-----
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to