RE: Binary size of statically linked java application

["Lehner, Michael" <michaellehner at siemens dot com>]

> -----Original Message-----
> From: java-owner@gcc.gnu.org [mailto:java-owner@gcc.gnu.org] On Behalf
Of
> Marco Trudel
> Sent: Tuesday, November 28, 2006 7:13 PM
> To: Joel Dice
> Cc: Lehner, Michael; gnustuff@thisiscool.com; java@gcc.gnu.org
> Subject: Re: Binary size of statically linked java application
> 
> >
> > How many stubs did you need to write to cut out Swing, AWT,
> 
> 36. But the biggest part is because of AWTCallbackHandler and
> SwingCallbackHandler. Removing these classes before compiling GCJ
would
> make real sense...
> 
> 
> > and javax.crypto?
> 
> 15
> 

[Lehner, Michael] 
I first tried to get away from AWT, this was very easy. I had to write 3
classes and 4 functions I think. Crypto seems to get a bigger deal for
my case.
I think it would be helpful if there would be a libgcj.a, that means a
classpath, without any implementation, but only empty functions. When
minimizing de code you would only have to remove an original file from
it and use instead the one with the same name from the other library
with only the function names inside. But I didn't find something like
that till now but perhaps later there will be some time to remove all
the unneeded code or I will find later.

Michael