Hi,
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).
Cheers,
Alejandro Leiva
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
El 29/07/2008, a las 15:13, Brian J. France escribió:
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
Hi!
possibilities). I missed to remark that we'll implement phpize based on
CMake (if is necesary).
Some way to build an extension stand-alone - phpize or other - is
definitely necessary.
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
Hi!
possibilities). I missed to remark that we'll implement phpize
based on CMake (if is necesary).Some way to build an extension stand-alone - phpize or other - is
definitely necessary.
Of course, what I try to say is that we'll implement a phpize above
CMake if CMake by itself (with some macros) can't do the work.
cul8er,
Alejandro Leiva