El 29/07/2008, a las 15:13, Brian J. France escribió:
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
Hi Brian,
It is mandatory to compile and linking some extensions to any sapi to
obtain a working php executable/library (e.g. ext/standard) but normal
extensions will be pluggable. Configure switchers will be supported,
in the same way or in new way (dependent of CMake possibilities). I
missed to remark that we'll implement phpize based on CMake (if is
necesary).
cul8er,
--
Alejandro Leiva
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
