RE: Problems using the GCJ interpreter

[Øyvind Harboe <oyvind dot harboe at zylin dot com>]

> As Tom pointed out, when you directly reference classes in 
> your code, they are statically resolved and without libswt.a, 
> you get the errors you see. 

I had two motivations for using the GCJ interpreter: to save compilation
time by not compiling swt.jar(I would have used GCJ 3.3 and Mohans compiled
SWT, but I'm one patch short, the property parsing problem you cornered)
and to check out what the deployment size was.
The GIJ test I posted earlier indicates that there is some sort of JNI 
issue(i.e. swt does not launch properly). 

However, I did some numbers on HelloSWT.exe from Mohan and here is what I got:

- gij.exe + class files and swt.jar -> 1.5MB zipped
- one big static HelloSWT.exe -> 1.0MB zipped

To get HelloSWT.exe 1.0MB zipped, I had to run the command below first

strip HelloSWT.exe -o HelloSWT.exe

Perhaps there is a gcj option which makes the strip step unecessary.

Øyvind