public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Vikas Gandhi <VGandhi@quark.co.in>
To: vkt@india.hp.com, "Turner, Jay" <Jay.Turner@sabre-holdings.com>,
	 pthreads-win32@sources.redhat.com
Subject: RE: LGPL and a proprietary application
Date: Fri, 23 May 2003 04:18:00 -0000	[thread overview]
Message-ID: <7D5800A5B6E26644B2EB7A862856B0D407EF7ABC@SARASWATI> (raw)

Hi Vinaya 
  I also want ask one basic fundamental quaestion. 
1) Is usage of a product like "pthreads-win32" forces us to release our
source code or not. 
2) Next can we use it as per our with without intimating anyone.

Regards
Vikas

-----Original Message-----
From: Vinaya Kumar T [mailto:vkt@india.hp.com]
Sent: Thursday, May 22, 2003 11:14 PM
To: Turner, Jay
Cc: pthreads-win32@sources.redhat.com
Subject: Re: LGPL and a proprietary application


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-23  4:18 UTC|newest]

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

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=7D5800A5B6E26644B2EB7A862856B0D407EF7ABC@SARASWATI \
    --to=vgandhi@quark.co.in \
    --cc=Jay.Turner@sabre-holdings.com \
    --cc=pthreads-win32@sources.redhat.com \
    --cc=vkt@india.hp.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).