This is the mail archive of the
pthreads-win32@sources.redhat.com
mailing list for the pthreas-win32 project.
RE: Thank you guys, thank you!
- To: 'Ales Pour' <pour at princip dot cz>, pthreads-win32 at sourceware dot cygnus dot com
- Subject: RE: Thank you guys, thank you!
- From: Hicham Bouhmadi <H dot Bouhmadi at emarket dot fr>
- Date: Thu, 20 Jul 2000 14:00:06 +0200
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