libgcj / Classpath relicensing and cooperation

Sat Apr 1 00:00:00 GMT 2000

>>>>> "Hans" == Boehm, Hans <hboehm@exch.hpl.hp.com> writes:

Hans> Could someone explain the intent here, if not the motivation?
Hans> If I package a compiled version of the AWT in a dynamic library,
Hans> I can presumably still ship it with a proprietary application?
Hans> If I link it in statically, the whole program must be covered by
Hans> the GPL? If I use any part of the library other than the AWT,
Hans> I'm fine either way?
I can't speak for Classpath. I removed the classpath list from the
followups.
We aren't going to put the Classpath AWT into libgcj. (We will remove
it from the tree before we import Classpath into libgcj.) We want
libgcj to be usable by basically everybody.
You will be able to statically link applications using libgcj with no
problem. If you want AWT, for now you're on your own :-(
Tom