This is the mail archive of the
mailing list for the pthreas-win32 project.
Re: Pthread win32 lite and LGPL static linking
- From: Ross Johnson <ross dot johnson at homemail dot com dot au>
- To: Robin Rowe <rower at movieeditor dot com>
- Cc: Pthreads-Win32 list <pthreads-win32 at sources dot redhat dot com>
- Date: Tue, 28 Feb 2006 15:38:20 +1100
- Subject: Re: Pthread win32 lite and LGPL static linking
My apologies. I seem to have missed seeing this email in my inbox. I
noticed it when searching the list archives on another topic.
The short answer to the license change request is AFAIK, not without the
explicit consent of all the contributors.
But is that really going to be a problem for your project? IMO if you're
making the source code to the application public and you're keeping the
pthreads-win32 LGPL and the copyright info intact, with you're own
additions where necessary, then that is within the spirit of the LGPL.
My test for this is (based on an explanation of the GPL/LGPL direct from
RMS): can your end users make changes to the pthreads code and rebuild
and relink your application to a working version? If the answer is yes,
then that satisfies the purpose of the LGPL.
I personally have no objection to you doing this. Did anyone else
respond to this request, or object?
If you're very concerned about the finer legal points then this response
may not be good enough for you. I hope it is though.
Thanks for making pthreads-win32 available.
I lead the CinePaint project. We check-in 3rd-party lib sources into our
CVS so that when a CinePaint Windows developer does a check-out he or
she has everything necessary to create a build. I've cut down Pthreads
for Windows into a much smaller lite version that contains just the
source files needed to build CinePaint Glasgow, list enclosed below. Our
libpthread.lib file is about 300kb.
We prefer to use small libs with static linking. FLTK, another LGPL lib
we're using, offers a static linking exception to its LGPL license to
accommodate that. Would you be able to do that for us, too?