From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5795 invoked by alias); 19 Jan 2008 01:27:52 -0000 Received: (qmail 5785 invoked by uid 22791); 19 Jan 2008 01:27:52 -0000 X-Spam-Check-By: sourceware.org Received: from mo-p07-ob.rzone.de (HELO mo-p07-ob.rzone.de) (81.169.146.189) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 19 Jan 2008 01:27:20 +0000 X-RZG-CLASS-ID: mo07 X-RZG-AUTH: gMysVb8JT2gB+rFDu0PuvnPihAP8oFdePhw95HsN8T+WAEY7RMYJ2Yg= Received: from linuix.haible.de ([81.210.248.5]) by post.webmailer.de (mrclete mo7) (RZmta 15.4) with ESMTP id 601d3dk0IJbMLK ; Sat, 19 Jan 2008 02:27:13 +0100 (MET) (envelope-from: ) From: Bruno Haible To: pthreads-win32@sourceware.org Subject: use of pthreads-win32 in gnulib? Date: Sat, 19 Jan 2008 01:27:00 -0000 User-Agent: KMail/1.5.4 Cc: bug-gnulib@gnu.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801190227.10706.bruno@clisp.org> Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2008/txt/msg00001.txt.bz2 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