[news.eclipse.platform.swt] Re: What is in swt-pi.jar

["Ivan Markov" <ivanm@xxxxxxxxx>]

I do not understand this swt-pi stuff either.
Is GTK2 linked dynamically with the SWT JNI stubs? If so, I don't see the
problem - LGPL requires only that and nothing else.

Now that you mention Fox: Fox is LGPL with the exception that it explicitely
permits for static linking of proprietary code with it.

So for SWT/Fox you will have one jar: swt.jar and one DLL:
swt-fox-blahblah.so
Fox will be statically linked inside the .so file. No external dependencies
whatsoever, except on libc and the X11 stuff.

/Ivan

"Jan Schulz" <muelleimer@xxxxxxxxxxxxxxxxx> wrote in message
news:slrnbh5jsm.nja.muelleimer@xxxxxxxxxxxxxxxxxxxx
> Hallo!
>
> * Veronika Irvine <veronika_irvine@xxxxxxx> wrote:
> > You need both jar files when running SWT applications.
> > The swt-pi.jar contains a JNI binding for GTK OS level calls.
> > The reason for the two jars on GTK is for compatability with the LGPL
> > license of the GTK OS layer.  If you look at the about.html file in
> > org.eclipse.swt.gtk you will see a description of this.
>
> Thanks for pointing that out. I didn't realize that swt.gtk is partly
> under LGPL...
>
> So what will happen if I specify swt.jar from motif and swt-pi.jar
> from gtk in my classpath and then start a swt App?
>
> Will every 'license-problem' part of swt be released with the name
> 'swt-pi.jar' (FOX toolkit?)?
>
> I'm not really firm in that sections. I want to enable gtk and motif
> bindings under debian (with SWT Apps, eclipse is running with the
> right -ws value). For that I want to put swt.jar (under the name
> swt2.1.jar, to be in line with debians library naming) under
> 'update-alternative', which generates symlinks to the chosen
> implementation (swt2.1-motif.jar or swt2.1-gtk.jar up to now).
>
> So I'm now facing the problem what to do with swt-pi.jar...
>
> BTW. What is the policy for breaking API changes in SWT?
>
> Jan