Re: [PHP4BETA] new configure approach

At 22:36 12/05/99 , Stig Sæther Bakken wrote:

I have started working on making it possible to build shared PHP extensions without the presence of the PHP source code. The approach resembles that of apxs for Apache (which again is based on something from Perl?) Since Zend and PHP4 have both moved towards producing reusable libraries, a logical next step would be to install them and the header files necessary to use them when PHP installed. Anyway, I have changed Zend (not checked in yet) to "make install" libzend.a to $prefix/lib/zend and its header files to $prefix/include/zend, and PHP to install its include files in $prefix/include/php. The idea is to also install "phpxs" in $prefix/bin/ and make it possible to build extensions using phpxs in different modes for compiling, linking and installing files. Then, extensions can be distributed separately, completely self-contained, with their own configure scripts and so on. Distribution maintainers should dig that. The thing that bothers me about this right now is that copying config.h and other stuff generated with configure to $prefix/include/php is stupid. I have not yet figured out a solution for this, so let's hear it from you guys :-)

From Zend's point of view, we don't want Zend alone to be installed separately from PHP. As we've mentioned numerous times in the past, only one thing is obvious about Zend's license, and it's that it's going to be freely distributable with PHP. We're not yet sure on whether or not it'll be distributed freely separately from PHP. It might, and it might not. Using armerge to create a library that contains both PHP and libzend may be a possible solution, even though it has little meaning in UNIX (you can still access all of Zend's functions and globals regardless of the PHP code). I'll have to talk to Andi about this too. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/ For a PGP public key, finger bourbon@netvision.net.il -- PHP 4 Beta