From: Hicham Bouhmadi <H.Bouhmadi@emarket.fr>
To: 'Ales Pour' <pour@princip.cz>, pthreads-win32@sourceware.cygnus.com
Subject: RE: Thank you guys, thank you!
Date: Thu, 20 Jul 2000 05:00:00 -0000 [thread overview]
Message-ID: <2BC8E41D77D8D211A48B0090272ABE172651C9@PEGASE> (raw)
1- About static librairies. There is static librairies on Win32. You create
them using the MS link executable without the switch -dll
Note that not all dll can compiled as static librairies. dll that exploits
the fact that they are dll (use of attachement / detachement, dll segment as
the data_seg...etc) can't be compiled as librairies.
2- About fork(). the meaning of fork has nothing to do with CreateProcess.
Among other, there is no parent-child relationship on the Win32 processes.
It's quite hard to simulate a fork() on Win32. Cygnus does it on cygwin but
with many extra-work than simply calling CreateProcess...
-----Message d'origine-----
De: Ales Pour [ mailto:pour@princip.cz ]
Date: jeudi 20 juillet 2000 13:18
Ŕ: pthreads-win32@sourceware.cygnus.com
Objet: Re: Thank you guys, thank you!
> 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...
> Also, does anyone know of a useful implementation of the
> fork() Unix system call ?
Have a look at CreateProcess().
> And finally, does anyone know of an implementation of
> POSIX shared memory scheme for windows?
Don't know, sorry.
Regards,
Ales
next reply other threads:[~2000-07-20 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 5:00 Hicham Bouhmadi [this message]
2000-07-20 5:49 ` Ales Pour
-- strict thread matches above, loose matches on Subject: below --
2000-07-20 2:17 Hugues Talbot
2000-07-20 4:17 ` Ales Pour
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=2BC8E41D77D8D211A48B0090272ABE172651C9@PEGASE \
--to=h.bouhmadi@emarket.fr \
--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).