From: "Gili" <junk@bbs.darktech.org>
To: "pthreads-win32@sources.redhat.com"
<pthreads-win32@sources.redhat.com>,
"rpj@callisto.canberra.edu.au" <rpj@callisto.canberra.edu.au>
Subject: Re: Static linking under win32
Date: Mon, 06 Dec 2004 06:35:00 -0000 [thread overview]
Message-ID: <20041206063500.Q9bTdtUE20SYM-_BnBxHQhKSA8VLGHXK_UPq509Aq3g@z> (raw)
In-Reply-To: <41B3FAAE.8060308@callisto.canberra.edu.au>
And here is an ugly question that has to be asked... I recently
read this:
http://www.javalobby.org/forums/thread.jspa?threadID=15903&messageID=918
18939&tstart=0
The implication seems to be that if my product links against a
LGPL library (pthreads-win32 is such a library) then it must adhere to
certain restrictions as set down by the LGPL. Two items I am
specifically concerned with:
1) The LGPL library source-code must be restributed in full with the
product
2) I must grant users the right to reverse-engineer my product
Now, not to start a religious warfare here (since it is not my
intent), but I'd like to clarify if this your intent as well? If I use
it in my product, must I do these two things?
Thanks,
Gili
On Mon, 06 Dec 2004 17:22:38 +1100, Ross Johnson wrote:
>Gili wrote:
>
>>Hi,
>>
>> I'm sure this is a commonly asked question: how do I build
>>pthreads-win32 under VC++ (7.1 in my case)? I am surprised you don't
>>ship a project file with the source-code or discuss this in the FAQ :)
>>
>>
>Yes, it should be in the FAQ.
>
>Pthreads-win32 relies on dynamic linking to provide a seemless interface
>to it's POSIX functionality - using dllMain to do some per process and
>per thread initialisation and cleanup. Static linking requires your
>application to call some non-portable routines (see README.NONPORTABLE:
>pthread_win32_process_attach_np etc). That's one reason why static
>linking is not really 'officially' encouraged.
>
>However, there's a VS Workspace file provided that will build the DLL.
>It was contributed by a user and I use it for debugging sometimes.
>Perhaps you can modify that one and send me the result.
>
>Nor do the makefiles that I use to build and test include targets for
>static linking.
>
>Regards.
>Ross
>
>
next prev parent reply other threads:[~2004-12-06 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200412060337.iB63beF00812@callisto.canberra.edu.au>
2004-12-06 6:22 ` Ross Johnson
2004-12-06 6:35 ` Gili [this message]
[not found] <200412061747.iB6HlGug210260@mtagate1.de.ibm.com>
2004-12-06 18:53 ` Alexander Terekhov
[not found] <200412060635.iB66ZiF01425@callisto.canberra.edu.au>
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] ` <E1CbMx8-0006Ad-S5@m1.dnsix.com>
2004-12-06 20:08 ` Keresztfalvi Laszlo
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:
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=20041206063500.Q9bTdtUE20SYM-_BnBxHQhKSA8VLGHXK_UPq509Aq3g@z \
--to=junk@bbs.darktech.org \
--cc=pthreads-win32@sources.redhat.com \
--cc=rpj@callisto.canberra.edu.au \
/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).