public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Vinaya Kumar T <vkt@india.hp.com>
To: "Turner, Jay" <Jay.Turner@sabre-holdings.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: LGPL and a proprietary application
Date: Thu, 22 May 2003 17:40:00 -0000	[thread overview]
Message-ID: <3ECD0C45.10509@india.hp.com> (raw)
In-Reply-To: <0A4834C63AA59242BD8A4C9CF8494E29FF46A7@sghdqms02.global.ad.sabre.com>

Hello Jay,

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
vinaya


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?
>
>Thanks, Jay
>
>
>  
>


  reply	other threads:[~2003-05-22 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 17:27 Turner, Jay
2003-05-22 17:40 ` Vinaya Kumar T [this message]
2003-05-24  6:36   ` Ross Johnson
2003-05-23  4:18 Vikas Gandhi
2003-05-23  5:13 ` Hugues Talbot

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=3ECD0C45.10509@india.hp.com \
    --to=vkt@india.hp.com \
    --cc=Jay.Turner@sabre-holdings.com \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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