From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9972 invoked by alias); 6 Dec 2004 17:47:00 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 9548 invoked from network); 6 Dec 2004 17:46:34 -0000 Received: from unknown (HELO bbs.darktech.org) (216.58.90.187) by sourceware.org with SMTP; 6 Dec 2004 17:46:34 -0000 Received: from localhost ([127.0.0.1]) by bbs.darktech.org (JAMES SMTP Server 2.2.0) with SMTP ID 189; Mon, 6 Dec 2004 12:46:24 -0500 (EST) From: "Gili" To: "Phil Frisbie, Jr." , "pthreads-win32@sources.redhat.com" Date: Mon, 06 Dec 2004 17:47:00 -0000 Priority: Normal In-Reply-To: <41B49828.8010407@hawksoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Static linking under win32 X-SW-Source: 2004/txt/msg00165.txt.bz2 Message-ID: <20041206174700.DXNU7gNAtq31RiNb91xzKce5OLMm_v4iroSKu5DA4Ks@z> 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 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. Gili