Glynn Clements <glynn(a)sensei.co.uk> writes:
[...]
>The point is that you're supposed to be able to rebuild the executable
>using only GPL'd sources.
Well, freely available sources. Otherwise you wouldn't be able to use
LGPL'd libraries. :)
There's also a section in the GPL about:
----------
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
----------
So you could make lwlib a shared library, or 'pluggable' and you could just
open the shared library at runtime and get all the function pointers out,
and not violate the GPL. In theory. Someone is just writing to a
well-published API (similar to GTK+ theme shared libraries). As long as
the header files for the lwlib interface did not suck so badly as to
require anybody that included them to use a GPL license, this should be
fine.
[...]
> In any case, Lesstif is GPL'd. Even if it isn't yet as reliable as a real
> Motif, it should at least allow you to build a Motif-enabled executable.
Yes, but there was a 'qt-alike' toolkit that people were working on that
would be GPL'd. Perhaps those header files could be resurrected, or a
minimal functional equivalent could be done, but that would suck. Similar
to the hooplah about the GNU bignum library that RIPEM wanted to use way
back when.
-bp
--
William M. Perry <wmperry(a)gnu.org>
You know what would make a good story? Something about a clown who
make people happy, but inside he's real sad. Also, he has severe
diarrhea.