Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39431
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain firehawksystems.com from 204.11.219.140 cause and error)
Cc: PHP Internals List <internals@lists.php.net>
Message-ID: <4AA262C6-3A89-46F0-96DF-F853D61CFB85@firehawksystems.com>
To: Alejandro Leiva <gloob@litio.org>
In-Reply-To: <438FCAF1-BF0E-4C14-9035-7D25CBBAB20E@litio.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 29 Jul 2008 09:13:57 -0400
References: <438FCAF1-BF0E-4C14-9035-7D25CBBAB20E@litio.org>
Subject: Re: [PHP-DEV] PHP Cmake
From: list@firehawksystems.com ("Brian J. France")


On Jul 29, 2008, at 4:52 AM, Alejandro Leiva wrote:
> 	I'm working in porting php to cmake there is information in the  
> wiki @ http://wiki.php.net/internals/cmake, now is compiling Zend,  
> main, TSRM, ext/ctype, ext/date, ext/dom, ext/libxml, ext/phar, ext/ 
> standard and sapi/cli. I wrote a php script to convert automatically  
> the information in config.m4 && config.w32 from extensions to CMake  
> (now only take care of PHP_NEW_EXTENSION but is extensible) and a  
> script to convert configure checks to CMake. I expect in one week to  
> have a php cli compiling and linking. After that I'll implement  
> CTest (for running php tests) and CPack (for automatic packaging)  
> also finish to porting all the extensions and all the sapi.
>
> 	Also in two weeks I think that we can begin to test it and porting  
> to Windows, now is working in Linux and MacOS platform (probably in  
> all unix like platforms).


Building the core, one sapi and no extensions, then using phpize for  
building shared extension will still be a option, right?

Brian