Well, if you don't dynamically load classes, statically linking this 83Mb behemoth enables you to get rid of most of it. On Windows, with MinGW, where this is possible, I build a shared library (a python extension) that is statically linked with libgcj.a and the resulting .dll is only 4.6MB in size.
I wish the same were possible on Linux and Mac OS X but I have not been able to create a shared library that is statically linked against libgcj.a
Andi..
On Thu, 5 May 2005, Richard Henderson wrote:
On Thu, May 05, 2005 at 04:57:48PM -0300, Alexandre Oliva wrote:The savings of creating static libraries would be small if we refrained from building non-PIC object files.
But still largely useless. Who in their right mind is going to use an 83MB static library when a shared library is available.
This is exactly what --tag disable-static for compilations accomplishes, and we had a patch to use that in our tree for some time, but RTH ran into a (probably libtool) bug on alpha that led him to revert the change, and then didn't provide enough info for anyone else without access to an alpha box to figure out what the problem was and then try to fix it :-(
I don't recall the failure mode anymore, nor do I have the patch. If you feel like working on --tag disable-static, don't let me stop you. I'll whine if it breaks again, but not before.
r~
