Examples on how to test:
./configure --with-xml static
./configure --with-xml=/opt static
./configure --with-xml=shared shared
./configure --with-xml=shared,/opt shared
The difference between these two is that when the extension is shared, it
is not merged into libphpext.a. The shared extension is currently always
built. I can't find a way to do just one or the other with automake/libtool,
if someone has a clever idea, please come forward. :-)
"make install" installs the .so (as well as a lot of other cruft) in
$prefix/lib/php.
- libzend/TSRM build in their own directories
- ext/Makefile was generated twice
****NOTE******
If you use any kind of VPATH, you need to do a "make distclean" in your
libzend/TSRM directory, before running configure again.
* There are now -I directives for the absolute path of php4, php4/libzend and the builddir for
the Apache module, so we can #include any php/Zend header.
* Rename config.h to php_config.h
fhttpd module taken out of functions, functions is ready to go.
The only extensions I have tested are gd+freetype and odbc(solid).
Please try compiling in your favourite extensions and let me know how it
works.
sub-directories and started to move extension code into ext/<name>. For now,
I have moved the "standard" extension (which is quite a mix of everything
right now) and the GD extension into their own subdirs in ext/.
The configure script now also runs configure in the libzend directory
automatically and makes sure php4 and libzend use the same config.cache file.
To avoid running configure in libzend, use the --no-recursion option.
"make" in php4 also builds libzend now.
The Apache module doesn't compile right now, but a fix for that is
coming up.
