Re: Feeler for GMP support

From: Tim Smith (reply_in_group_at_mouse-potato.com)
Date: 07/25/05 

Date: Mon, 25 Jul 2005 20:01:33 GMT

In article <42dcc731$0$2962$ed2619ec@ptn-nntp-reader01.plus.net>, BRG wrote:
> On looking at this I find that GMP is distributed under the LGPL (Library
> or Lesser GPL).
>
> I am no expert on this but I think the LGPL does allow both static and
> dynamic linking to proprietary code.

The one-sentence summary would be that if you distribute an LGPL library as
part of your product, you have to provide a way for the users to relink with
other versions of that library (and I think you have to provide source to
that library).

If you can accomplish that with static linking, fine, but usually you can't
reasonably do so except for open source products, so proprietary projects
usually have to go with dynamic linking. 

-- 
--Tim Smith

Relevant Pages

  • Re: GPL encumbrance problems
    ... It doesn't matter *which* of GPL, ... This is the LGPL dynamically linked case: ... static linking. ... In the case of dynamic linking, it ...
    (Fedora)
  • Re: Identifying CL Implementations?
    ... >>> I'm not sure I understand what the fuss over the LGPL is. ... >> What does it mean to statically link Lisp, Smalltalk, or Java? ... Hence, the LLGPL, which defines the LGPL's ... and dynamic linking differently. ...
    (comp.lang.lisp)
  • Re: OT: Two ways Microsoft sabotages Linux desktop adoption
    ... LGPL doesn't, but one must still, in effect, provide source ... a derivative work, even with dynamic linking. ... a derivative of glibc's sources or binaries. ...
    (Fedora)
  • Re: GPL encumbrance problems
    ... >> which is LGPL. ... > force any *other* libraries I might link with to be distributed in ... engineering constraint from section 6 therefore only applies to ... In the case of dynamic linking, it ...
    (Fedora)