public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: pthreads-win32@sourceware.org
Cc: bug-gnulib@gnu.org
Subject: use of pthreads-win32 in gnulib?
Date: Sat, 19 Jan 2008 01:27:00 -0000	[thread overview]
Message-ID: <200801190227.10706.bruno@clisp.org> (raw)

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

             reply	other threads:[~2008-01-19  1:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19  1:27 Bruno Haible [this message]
2008-01-21 13:02 ` Burkhardt, Glenn
2008-01-21 13:51 ` Ross Johnson

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=200801190227.10706.bruno@clisp.org \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=pthreads-win32@sourceware.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).