Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 74483 invoked from network); 30 Nov 2006 21:58:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Nov 2006 21:58:42 -0000 Received: (qmail 99743 invoked by uid 500); 30 Nov 2006 21:58:50 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 99692 invoked by uid 500); 30 Nov 2006 21:58:50 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 99681 invoked by uid 99); 30 Nov 2006 21:58:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 13:58:49 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [207.155.248.12] (HELO devonshire.cnchost.com) (207.155.248.12) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2006 13:58:37 -0800 Received: from [192.168.0.21] (c-24-15-193-17.hsd1.il.comcast.net [24.15.193.17]) (as wrowe@rowe-clan.net) by devonshire.cnchost.com (ConcentricHost(2.54) Relay) with ESMTP id C2D1B3E1B for ; Thu, 30 Nov 2006 16:58:08 -0500 (EST) Message-ID: <456F53EE.6080201@rowe-clan.net> Date: Thu, 30 Nov 2006 15:58:06 -0600 From: "William A. Rowe, Jr." User-Agent: Thunderbird 1.5.0.8 (X11/20061107) MIME-Version: 1.0 To: dev@apr.apache.org Subject: Re: windows && threads References: <20061130041024.GB16503@cox.net> In-Reply-To: <20061130041024.GB16503@cox.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Bob Rossi wrote: > Hi, > > I'm trying to configure/build apr on windows with threads. I already see > that apr can be built with cl and windows threads. However, currently > I'd like to avoid using cl, since my project uses the autotools. > > I have a few questions, > > - can apr be built with mingw and cygwin posix threads? > - can apr be built with mingw and native posix threads? > - can apr be built with cygwin g++ and cygwin posix threads? > - can apr be built with cygwin g++ and native posix threads? > - can apr be built with either mingw or g++ and with any thread library? > > If it's not already documented, it should be added somewhere, as I've > spent several hours trying to solves this problem already. I'm sure it > would benefit a lot of people. There has been some work in this direction - there are more patches pending in http://issues.apache.org/bugzilla/. The issue with using cygwin beyond-compiling is that you are stacking two portability layers on top of each other. Mileage may vary, but it should look similar to a Hummer. Similarly with non-native threads, if you are running under the Win32-NT subsystem. If you really want to run efficiently and effectively under posix, I suggest SFU which is a native port, or investigate vmware or the future subsystem solutions coming out from Netware. And as we say - patches are ALWAYS welcome for consideration if you can get past specific issues, but I'd encourage that ./configure should detect that it is building to the Win32 API unless otherwise informed with --options. Bill