Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36211 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25748 invoked from network); 20 Mar 2008 01:23:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Mar 2008 01:23:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=gwynne@wanderingknights.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=gwynne@wanderingknights.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain wanderingknights.org from 208.97.132.177 cause and error) X-PHP-List-Original-Sender: gwynne@wanderingknights.org X-Host-Fingerprint: 208.97.132.177 sd-green-bigip-177.dreamhost.com Linux 2.4/2.6 Received: from [208.97.132.177] ([208.97.132.177:50442] helo=postalmail-a5.g.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/99-14744-C8CB1E74 for ; Wed, 19 Mar 2008 20:23:24 -0500 Received: from [192.168.2.192] (c-24-128-82-179.hsd1.ma.comcast.net [24.128.82.179]) by postalmail-a5.g.dreamhost.com (Postfix) with ESMTP id 3C71EBF21C; Wed, 19 Mar 2008 18:23:21 -0700 (PDT) Cc: Scott MacVicar , PHP Developers Mailing List Message-ID: To: jani.taskinen@iki.fi In-Reply-To: <47E1BB35.2070503@sci.fi> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 19 Mar 2008 21:23:16 -0400 References: <47E1BB35.2070503@sci.fi> X-Mailer: Apple Mail (2.919.2) Subject: Re: [PHP-DEV] CMake SoC Proposal From: gwynne@wanderingknights.org (Gwynne Raskind) My two US cents :). On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote: >> Here is a quick run down of some of the features of CMake and tools =20= >> associated with it: >> =95 A single configure script that would be used regardless of the OS >> =95 A much simpler scripting language > m4 is simple. :-p Since when? >> =95 Generates native build files (make, XCode, Visual Studio 6, 7.1, = 8) > err..a simple Makefile isn't "native" enough? Like we have right =20 > now? :) > Care to explain what you meant with this? Make is outmoded, outdated, and not up to the task of modern builds. =20 You can't use a Makefile (effectively) with Xcode. >> =95 Use a build directory so that all build related files are outside = =20 >> the main source tree, no more pollution of your checkout. > You can do that already even with autoconf generated configure: Just =20= > call the configure script from wherever you want to build the stuff. =20= > (I build PHP always outside the source tree to not pollute my =20 > checkout. :) As do I, but I still have to pollute my checkout with buildconf or =20 csript buildconf.js. >> Bill Hoffman of Kitware who produce CMake and the related tools =20 >> have offered their assistance in our transition, including adding =20 >> ports to any unsupported operating systems or features that would =20 >> prevent us from currently doing the move. > phpize is the one and only thing that comes to my mind as an =20 > obstacle..but it's propably possible to simulate using this CMake =20 > thingie? Everyone has CMake installed, right? :D If automake and autoconf can do it, then as a rule CMake can do it =20 better. -- Gwynne, Daughter of the Code "This whole world is an asylum for the incurable."