From: Rian Hunter <rian@thelaststop.cjb.net>
To: Bobby Krupczak <rdk@krupczak.org>
Cc: pthreads mailing list <pthreads-win32@sources.redhat.com>
Subject: Re: archive? questions from new win32/pthreads user
Date: Tue, 24 Aug 2004 19:49:00 -0000 [thread overview]
Message-ID: <1093376917.83953.7.camel@www.thelaststop.net> (raw)
In-Reply-To: <1093375346.83953.2.camel@www.thelaststop.net>
On Tue, 2004-08-24 at 15:22, Rian Hunter wrote:
> On Tue, 2004-08-24 at 10:42, Bobby Krupczak wrote:
> > Hi!
> >
> > > Probably you need to put the file pthreadsVC.dll (you can download it
> > > from ftp://sources.redhat.com/pub/pthreads-win32/dll-latest/lib/) in
> > > your system directory.
> >
> > Thanks; that does work as well as putting it in the current
> > directory. However, I was wanting to statically link so I would not
> > need to install a dll.
>
> pthreads-win32 isn't distributed as a static library in binary form.
> you're going to have to compile it with your application or just compile
> a static library. open the pre-made project file from the source distrib
> and change the target to a static library (using vc++). hope that helps.
oh yeah i forgot to mention. according to section 6a of the LGPL, if you
are going to publicly release whatever project you are working on and
you statically link pthreads-win32 you must also distribute the seperate
linkable object code of your program along with the pthreads-win32
library source.
-rian
next prev parent reply other threads:[~2004-08-24 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 14:40 Gianluca
2004-08-24 14:42 ` Bobby Krupczak
2004-08-24 19:23 ` Rian Hunter
2004-08-24 19:49 ` Rian Hunter [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 13:34 Bobby Krupczak
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=1093376917.83953.7.camel@www.thelaststop.net \
--to=rian@thelaststop.cjb.net \
--cc=pthreads-win32@sources.redhat.com \
--cc=rdk@krupczak.org \
/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).