This is the mail archive of the
mailing list for the pthreas-win32 project.
Re: LGPL and a proprietary application
- From: Vinaya Kumar T <vkt at india dot hp dot com>
- To: "Turner, Jay" <Jay dot Turner at sabre-holdings dot com>
- Cc: pthreads-win32 at sources dot redhat dot com
- Date: Thu, 22 May 2003 23:13:33 +0530
- Subject: Re: LGPL and a proprietary application
- Organization: Hewlett Packard India Software Operations Private Ltd.
- References: <0A4834C63AA59242BD8A4C9CF8494E29FF46A7@sghdqms02.global.ad.sabre.com>
- Reply-to: vkt at india dot hp dot com
ru linking to this LGPL library statically or dynamically...??
if statically linked ,then u should make only that of the ur src code
open ,so that , changes in LGPL can
be done effectively.
On other hand ,if it dynamically linked,then u don't have to worry about
ur src code to be made open.
hope this helps
Turner, Jay wrote:
In reading the LGPL for pthreads-win32 I find I am confused. My application is company proprietary and one reading says that an application that "uses the library" does not itself fall under the LGPL. Another reading says that it does (mainly because it uses pthread.h and semaphore.h).
Can I link to pthreads-win32 in my application without the license requiring that I provide my source or object code to my customers?
Is there anything that my legal department would accept that would confirm this?