public inbox for
 help / color / mirror / Atom feed
From: Keresztfalvi Laszlo <>
To: Gili <>
Cc: pthreads-win32 <>
Subject: Re: Static linking under win32
Date: Mon, 06 Dec 2004 20:08:00 -0000	[thread overview]
Message-ID: <20041206200737.GC3980@cross> (raw)
In-Reply-To: <>

On Mon, Dec 06, 2004 at 12:46:24PM -0500, Gili wrote:
> On Mon, 06 Dec 2004 09:34:32 -0800, Phil Frisbie, Jr. wrote:
> [...] 
> >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

Sorry, I was quoted.. twice.. so it's not my mail :))

I've take a short tour on and found this link clean and short to
overview :)

About the GPL compatible licenses:

The first two on the list is what we are talking about. It clearly states
for LGPL: "it permits linking with non-free modules". Follow the special
circumstances link where:

"The GNU Project has two principal licenses to use for libraries. One is the
GNU Library GPL; the other is the ordinary GNU GPL. The choice of license
makes a big difference: using the Library GPL permits use of the library in
proprietary programs; using the ordinary GPL for a library makes it
available only for free programs."

I think this clearly explains what you are scared about. Note that LGPL
changed its full name to Lesser GPL to better reflect that it is not only
for libraries but here it was called Library GPL.

Back to Gili:
> 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

I think you mix the GPL and LGPL at some point. Providing the source of the
used (linked in) LGPL library just means you make available the LGPL'd lib
which you've used and usually available from its author too.. Not your code!

About the reverse engineering I agree with Ross that this is more about
future linking without access to the source. (Usually a quite ugly hack play
with symbols.. chosen only when nothing else possible :)


  parent reply	other threads:[~2004-12-06 20:08 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
2004-12-06 18:07       ` Alexander Terekhov
     [not found]       ` <>
2004-12-06 20:08         ` Keresztfalvi Laszlo [this message]
     [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=20041206200737.GC3980@cross \ \ \ \

* 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).