public inbox for
 help / color / mirror / Atom feed
From: "Gili" <>
To: "Phil Frisbie, Jr." <>,
Subject: Re: Static linking under win32
Date: Mon, 06 Dec 2004 17:47:00 -0000	[thread overview]
Message-ID: <20041206174700.DXNU7gNAtq31RiNb91xzKce5OLMm_v4iroSKu5DA4Ks@z> (raw)
In-Reply-To: <>

On Mon, 06 Dec 2004 09:34:32 -0800, Phil Frisbie, Jr. wrote:

>Sony Entertainment had no problem including my LGPL library as a DLL in their 
>game PlanetSide. They include a copyright notice and the URL to my website so 
>that users can get the full source to the hvdi.dll file.
>This is what the LGPL is all about.
>> Regards,
>> Laszlo


	I think the point of conflict is more about what people
*percieve* LGPL to be about. FSF keeps on stating things like "you give
users the right to reverse-engineer your final-product" or "you must
ship the full source-code of the LGPL component with your
final-product" if you use LGPL code. I've seen explicit mentions
stating that linking to the source-code is not good enough, you *must*
bundle it. I've also seen explicit mentions of static, dynamic link
and/or inheritance (under OOP) from a LGPL library causing your final
product to be considered a "derived work" hence all of the above
restrictions apply to it. It is statements such as these that scare the
bejesus out of me, and coming out of FSF it is something to take
seriously. I take no offence from the actual authors of the LGPL
library because quite often I've found that they did not mean to imply
(or were not aware of) the conditions stipulated by FSF.


  reply	other threads:[~2004-12-06 17:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2004-12-06  7:52 ` Ross Johnson
2004-12-06  9:57   ` Alexander Terekhov
2004-12-06 10:46   ` Keresztfalvi Laszlo
2004-12-06 17:35     ` Phil Frisbie, Jr.
2004-12-06 17:47       ` Gili [this message]
2004-12-06 18:07       ` Alexander Terekhov
     [not found]       ` <>
2004-12-06 20:08         ` Keresztfalvi Laszlo
     [not found] <>
2004-12-06 18:53 ` Alexander Terekhov
     [not found] <>
2004-12-06  6:22 ` Ross Johnson
2004-12-06  6:35   ` Gili
2004-12-06  3:37 Gili

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041206174700.DXNU7gNAtq31RiNb91xzKce5OLMm_v4iroSKu5DA4Ks@z \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).