On Thu, Feb 20, 2003, Ralf S. Engelschall wrote:
> Does this mean our "php" package now provides Zend in a form (library
> plus includes) for possible inclusion/embedding into other applications?
> If yes, nice. If not, for whom are the headers intended?
>From what I have seen and tested you can create php modules using the
headers alone and there are no libraries. The php module will be linked
as a shared object and dynamically loaded by php itself.
It's not optimal to use because you have to specify all include
(sub-)directories. E.g.
gcc -I/cw/include/php \
-I/cw/include/php/main \
-I/cw/include/php/Zend \
-I/cw/include/php/TSRM \
-I/cw/include/php/regex \
-c module.c
ld -shared -o module.so module.o
I could try to coalesce all includes into a single
directory but then I had to modify the includes that currently do
reference things like "../main/php_config.h"
What is missing in the php package is the standard directory for
php modules. The apache package will create that directory, i.e.
something like:
/cw/lib/php/extensions/no-debug-non-zts-20020429
I currently try to figure out the best way to extract that path from
the build process.
--
Michael van Elst
[EMAIL PROTECTED]
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
