Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39438
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain litio.org from 91.121.171.199 cause and error)
Cc: PHP Internals List <internals@lists.php.net>
Message-ID: <294A74FA-02D0-4EC1-BEC9-8762C4C6E571@litio.org>
To: Brian J. France <list@firehawksystems.com>
In-Reply-To: <4AA262C6-3A89-46F0-96DF-F853D61CFB85@firehawksystems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 29 Jul 2008 17:23:19 +0200
References: <438FCAF1-BF0E-4C14-9035-7D25CBBAB20E@litio.org> <4AA262C6-3A89-46F0-96DF-F853D61CFB85@firehawksystems.com>
Subject: Re: [PHP-DEV] PHP Cmake
From: gloob@litio.org (Alejandro Leiva)


El 29/07/2008, a las 15:13, Brian J. France escribi=F3:

>
> On Jul 29, 2008, at 4:52 AM, Alejandro Leiva wrote:
>> 	I'm working in porting php to cmake there is information in the =20=

>> wiki @ http://wiki.php.net/internals/cmake, now is compiling Zend, =20=

>> main, TSRM, ext/ctype, ext/date, ext/dom, ext/libxml, ext/phar, ext/=20=

>> standard and sapi/cli. I wrote a php script to convert =20
>> automatically the information in config.m4 && config.w32 from =20
>> extensions to CMake (now only take care of PHP_NEW_EXTENSION but is =20=

>> extensible) and a script to convert configure checks to CMake. I =20
>> expect in one week to have a php cli compiling and linking. After =20
>> that I'll implement CTest (for running php tests) and CPack (for =20
>> automatic packaging) also finish to porting all the extensions and =20=

>> all the sapi.
>>
>> 	Also in two weeks I think that we can begin to test it and =
porting =20
>> to Windows, now is working in Linux and MacOS platform (probably in =20=

>> all unix like platforms).
>
>
> Building the core, one sapi and no extensions, then using phpize for =20=

> building shared extension will still be a option, right?
>
> Brian

Hi Brian,

	It is mandatory to compile and linking some extensions to any =
sapi to =20
obtain a working php executable/library (e.g. ext/standard) but normal =20=

extensions will be pluggable. Configure switchers will be supported, =20
in the same way or in new way (dependent of CMake possibilities). I =20
missed to remark that we'll implement phpize based on CMake (if is =20
necesary).

cul8er,
--
Alejandro Leiva