Re: Compiling "static" applications with SWT/GTK

[Erik Poupaert <erik dot poupaert at skynet dot be>]

> >It sounds like you are trying to deploy a single executable.  That's not
> >really a good justification for shared libraries.  But it's also not the
> >common case.  If you are deploying many, perhaps dozens, of gcj-compiled
> >executables you surely don't want each to be many megabytes in size.
> >
>     Well, the executable size isn't THAT ridiculous if you use "strip" 
> on them, and there are various on-the-fly-compression tools (like UPX) 
> that you can use to make this disadvantage a non-factor (granted, they 
> aren't quite as effective on Linux as on Win32 for reasons that are way 
> off-topic).

dlls, so's, jres, jars are becoming all-pervasive as a deployment method, while
linking statically is becoming more and more difficult, even more so on linux than on
win32. It takes all kinds of increasingly difficult tricks and workarounds to link
statically (try SWT 3.0, for example).

Indeed, stronger forces are pushing us in that direction. You can try to struggle ...
I think, however, that in the end, we will be assimilated.