This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Compiling "static" applications with SWT/GTK
- From: Andrew Haley <aph at redhat dot com>
- To: "Steve D. Perkins" <mailinglists at steveperkins dot net>
- Cc: gnustuff at thisiscool dot com, Ranjit Mathew <rmathew at hotmail dot com>, java at gcc dot gnu dot org
- Date: Mon, 1 Dec 2003 20:10:08 +0000
- Subject: Re: Compiling "static" applications with SWT/GTK
- References: <1YVSB7RLPK71VQ967208832ZTRJIEA4Y.3fcb3679@p733><3FCB9E11.7070901@steveperkins.net>
Steve D. Perkins writes:
> Mohan Embar wrote:
>
> >I'm probably going to get tarred and feathered for this, but
> >I don't understand the deployment problem either. Even on
> >Windows, I typically make my deployment "unit" a small executable
> >plus a number of DLLs all deployed in the same directory.
> >This seems to me the best of all worlds, especially if the distributed
> >bundle contains not one, but possibly several interrelated
> >executables as is often the case.
> >
> I guess the main thing I don't understand is why static vs. dynamic
> linking is something that you choose as a configure option when building
> the compiler from source.
It's there because dynamic linkage isn't supported on every system.
> I mean, my GCJ installation in my Linux environment ships with a
> libgcj static library and a libgcj shared library, and GCJ has a
> "-static" flag... so what's the problem? If there are problems
> with the "-static" flag, or static compilation in general, it would
> seem to make more sense to resolve those issues... rather than
> leave it broken and tell people "it's like that on purpose", or
> "it's for your own good".
It can't be done. I have explained why it can't be done on several
occasions.
Andrew.