Re: CMake SoC Proposal
| From: | Pierre Joye | Date: | Wed, 26 Mar 2008 11:12:47 +0000 |
| Subject: | Re: CMake SoC Proposal | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-36530@lists.php.net to get a copy of this message | ||
On Thu, Mar 20, 2008 at 2:45 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> Gwynne Raskind wrote:
> > 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
> >>> associated with it:
> >>> • A single configure script that would be used regardless of the OS
> >>> • A much simpler scripting language
> >> m4 is simple. :-p
> >
> > Since when?
>
> m4 is actually one of the simplest languages around. There really isn't
> much to it. The pain point of autoconf/automake/libtool isn't m4, it is
> the complicated and often obtuse relationship between those 3 tools.
>
> I don't mind exploring cmake, but it is a massive undertaking to create
> something that can build PHP on every UNIX and pseudo-UNIX platform out
> there. We should figure out what the main goal here is. If it is
> simply getting "native" build files so people can use their
> pointy-clickety interfaces to build PHP, then it is probably way easier
> to create .in files to generate those basic build templates from our
> current system than it is to rewrite the whole thing.
To have a pointy-clickety (I like this word :) interface is
definitively not a goal. It is a side effect of using CMake as CMake
has a GUI available on unix and windows. The main goal is actually to
have one single tool for all platforms and to lower the barriers of
the build scripts.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org