Re: CMake SoC Proposal
| From: | Gwynne Raskind | Date: | Thu, 20 Mar 2008 01:23:16 +0000 |
| Subject: | Re: CMake SoC Proposal | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-36211@lists.php.net to get a copy of this message | ||
My two US cents :).
On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote:
Since when?Here is a quick run down of some of the features of CMake and tools associated with it: • A single configure script that would be used regardless of the OS • A much simpler scripting languagem4 is simple. :-p
Make is outmoded, outdated, and not up to the task of modern builds. You can't use a Makefile (effectively) with Xcode.• Generates native build files (make, XCode, Visual Studio 6, 7.1, 8)err..a simple Makefile isn't "native" enough? Like we have right now? :) Care to explain what you meant with this?
As do I, but I still have to pollute my checkout with buildconf or csript buildconf.js.• Use a build directory so that all build related files are outside the main source tree, no more pollution of your checkout.You can do that already even with autoconf generated configure: Just call the configure script from wherever you want to build the stuff. (I build PHP always outside the source tree to not pollute my checkout. :)
If automake and autoconf can do it, then as a rule CMake can do it better. -- Gwynne, Daughter of the Code "This whole world is an asylum for the incurable."Bill Hoffman of Kitware who produce CMake and the related tools have offered their assistance in our transition, including adding ports to any unsupported operating systems or features that would prevent us from currently doing the move.phpize is the one and only thing that comes to my mind as an obstacle..but it's propably possible to simulate using this CMake thingie? Everyone has CMake installed, right? :D