[C++-sig] BPL binary size (was: Re: help building hello world example on Debian)

[Niall Douglas]

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

On 11 Apr 2004 at 0:19, Daniel Holth wrote:

> http://www.xiph.org/~brendan/shout-python/ wraps the same library
> using the Python C api directly; my boost.python binary is 29 times
> larger than that when compiled by distutils and the boost-jam debug
> build is 165 times larger. When you run 'strip' on shoutpy.so the
> extension is only 18 times larger than the C version of almost the
> same thing. But as we know the boost.python wrapper gets written much
> more quickly and in a less dodgy way than often ad-hoc
> direct-to-Python-API code, and if we didn't care about programmer
> efficiency we wouldn't be using Python in the first place.

GCC produces much larger binaries for the same code than other 
compilers. GCC v3.4 has improved this very significantly (50%) over 
previous GCC's, but MSVC still regularly makes a binary between 50 
and 100% smaller than GCC v3.4.

My BPL based bindings are 15Mb with MSVC and no less than 56Mb for 
identical code. Says it all really :(

Cheers,
Niall





-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBQHnYqMEcvDLFGKbPEQJr9QCg9Pp66yHngOafFGAyT/2U3KRXrR4AoKv/
0Ay0V5Nj1RXbszvSyAitUrM9
=QcYS
-----END PGP SIGNATURE-----