Re: gtkmm capabilities
- From: Roel Vanhout <roel riks nl>
- To: Paul Davis <paul linuxaudiosystems com>
- Cc: gtkmm-list <gtkmm-list gnome org>
- Subject: Re: gtkmm capabilities
- Date: Tue, 01 Feb 2005 14:22:04 +0100
Paul Davis wrote:
many windows applications use dynamic/runtime linkage to .dll's, and
you can do this with an LGPL library without any consequences to your
own code.
Oh yes, and for DLL's, there is little discussion. But the OP asked
specifically about static linking.
i agree that the LGPL is not as clear about this as it could be, but
the intent is absolutely clear: you can use the library, you can
modify the library, but you must make whatever version of the library
you linked with available so that the user could relink against their
own, suitably modified version.
This is the short version, and as far as your explanation goes, it is
correct. However this was not the matter under debate; the question is
what license the rest of your progrem (ie, the part that commercial
developers want to keep closed) has to be under in order to be allowed
to use LGPL libraries. My standpoint is that that license will have to
have certain characteristics that commercial developers will not appreciate.
cheers,
roel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]