Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6116 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22960 invoked by uid 1010); 3 Dec 2003 16:45:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 22902 invoked from network); 3 Dec 2003 16:45:00 -0000 Received: from unknown (HELO milton.schell.de) (217.160.72.35) by pb1.pair.com with SMTP; 3 Dec 2003 16:45:00 -0000 Received: (qmail 32056 invoked by uid 501); 3 Dec 2003 16:45:00 -0000 Received: from unknown (HELO fragrance) (217.160.72.104) by kdserv.de with SMTP; 3 Dec 2003 16:45:00 -0000 Date: Wed, 3 Dec 2003 17:45:00 +0100 (CET) X-X-Sender: sas@fragrance To: Wez Furlong cc: internals@lists.php.net In-Reply-To: <0b8401c3b9bb$dc5dbee0$8802a8c0@obsidian> Message-ID: References: <0b8401c3b9bb$dc5dbee0$8802a8c0@obsidian> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] mingw32 From: sascha@schumann.cx (Sascha Schumann) On Wed, 3 Dec 2003, Wez Furlong wrote: > When I tried to enable win32 specific extensions (such as COM) > under cygwin, I found that a lot of the win32 api headers were > missing, so the build failed. Cygwin is a Unix portability layer, not a win32. :) mingw's header set should be fairly complete. http://www.mingw.org/mingwfaq.shtml#faq-w32api > I don't plan to look at mingw32 myself, and I don't want to > deal with patches for it until I've completed the features > I have planned for the build system; once done, adding mingw > support should be reasonably simple (just change the object > and library suffixes and compiler flags...). Will there be an abstraction similar to our current m4 infrastructure? (I have not looked at the .js yet) - Sascha