public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
* use of pthreads-win32 in gnulib?
@ 2008-01-19  1:27 Bruno Haible
  2008-01-21 13:02 ` Burkhardt, Glenn
  2008-01-21 13:51 ` Ross Johnson
  0 siblings, 2 replies; 3+ messages in thread
From: Bruno Haible @ 2008-01-19  1:27 UTC (permalink / raw)
  To: pthreads-win32; +Cc: bug-gnulib

Hi,

The GNU gnulib project [1][2] provides a portability library for porting
programs written against the POSIX API to all kinds of platforms. One of
these platforms is mingw (native Win32 API).

All reasonable porting targets nowadays implement the POSIX threads API,
except for mingw. (The others that don't are Solaris 2.4 and BeOS. But these
are not reasonable porting targets any more.) Therefore your library would
nicely fit into gnulib.

What gnulib provides so far, relating to multithreading, is only a portable
layer for handling locks (mutexes) and TLS. But generally it's preferrable
to use the POSIX API rather than some other API; this is another reason
why your library is interesting for gnulib.

How well tested is pthreads-win32? Is there a list of packages that uses it?

Can it be built on mingw with pretty clean, standard Makefile infrastructure?
Does building with "gcc -Wall" produce only a small amount of warnings?

If gnulib started to "virtually" include your library (i.e. make it available
in source code when a gnulib user requests the gnulib module 'pthreads'),
would that be OK with you?

Regards,
                     Bruno


[1] http://www.gnu.org/software/gnulib/
[2] http://savannah.gnu.org/projects/gnulib

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-01-21 13:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-19  1:27 use of pthreads-win32 in gnulib? Bruno Haible
2008-01-21 13:02 ` Burkhardt, Glenn
2008-01-21 13:51 ` Ross Johnson

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).