From: Tristan Savatier <tristan@mpegtv.com>
To: Ales Pour <pour@princip.cz>
Cc: pthreads-win32@sourceware.cygnus.com
Subject: Re: [pthread-win32] Re: Thank you guys, thank you!
Date: Thu, 20 Jul 2000 12:45:00 -0000 [thread overview]
Message-ID: <3977580D.586337A6@mpegtv.com> (raw)
In-Reply-To: <3976DFD5.64FCB73F@princip.cz>
Ales Pour wrote:
>
> > Now for some additional question: how is it possible to compile
> > against the pthread.lib, not the DLL, to produce a (more) static
> > executable, so that I don't have to ship pthread.dll? Sorry if this
> > is an elementary question, I'm new to this.
>
> As far as I know, .lib files are import libraries that doesn't contain
> any code (which resides in according .dll); there's no way to have win32
> static binary as we know it from unix...
What do you mean ?
We are using static pthread.lib libraries in our Windows development,
and it works just fine. our application is linked with
pthread.lib and does not require any pthread.dll.
pthread.lib was generated like any other .lib library, by
linking together all the .obj files of the pthread package.
The only special thing that we had to do is:
the application must call _pthread_processInitialize()
before calling any other pthread_win32 function.
Normally this routine is called automatically when the dll is
attached, so here it must be called explicitely.
-t
next prev parent reply other threads:[~2000-07-20 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 2:17 Hugues Talbot
2000-07-20 4:17 ` Ales Pour
2000-07-20 12:45 ` Tristan Savatier [this message]
2000-07-20 12:47 ` [pthread-win32] Unsubscribe Xianglong Huang
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=3977580D.586337A6@mpegtv.com \
--to=tristan@mpegtv.com \
--cc=pour@princip.cz \
--cc=pthreads-win32@sourceware.cygnus.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).