All the examples I have found regarding writing PHP extensions
assume that I should want to rebuild the PHP core module.
I consider this approach undesirable for several reasons:
a) I don't expect to recompile IIS, or SqlServer just to build an add-on
b) if I get the rebuild wrong, I risk corrupting an environment that currently at least works
c) I would have to understand the intricacies of autoconf/make etc. for Unix/Apache/PHP
all of which are far beyond my interest/experience.
If there was a decent template/tutorial eg: Hello World that I could then extend,
I could apply my C/C++ knowledge to extending that template, rather than having
first to become a Linux/Apache/PHP guru at a level that I simply don't aspire to.
If someone has or could build and document such an example (I am running
Suse Linux 9.3, with PHP/MySql as distributed in that package), I would be
delighted to hear about it.
If none such exists, I should even be happy to commission such, for money.
(I know Linux prides itself on being free, but in the real world, beer and sandwiches
cost money, and this roadblock is preventing a client project from progressing, so
I believe remuneration to be in order, if it moves us forward).
Cheers,
Andrew Mather.
ps: the example given at http://www.zend.com/php/internals/ makes sense, as such,
but while the first two command (phpize, ./configure, seem to work, the make command
throws errors like confetti, based on the lack of php.h, zend.h etc in an environment that
was installed 'out of the box' of Suse 9.3, rather than to the bespoke 'we can rebuild it'
requirements of the example.
Making such an example compile and run as a dynamically loadable module in the
described environment would be my goal, allowing me to extend it as required later.
Andrew Mather wrote:
ps: the example given at http://www.zend.com/php/internals/ makes sense, as such,
but while the first two command (phpize, ./configure, seem to work, the make command
throws errors like confetti, based on the lack of php.h, zend.h etc in an environment that
was installed 'out of the box' of Suse 9.3, rather than to the bespoke 'we can rebuild it'
requirements of the example.Making such an example compile and run as a dynamically loadable module in the
described environment would be my goal, allowing me to extend it as required later.
Perhaps you didn't install the -dev package in SUSE? I know nothing
about SUSE and how they chose to package PHP, but if you installed PHP
from our sources, it would have installed those files. I am sure SUSE
has those hidden away somewhere.
-Rasmus
Hello Rasmus,
Thursday, February 9, 2006, 1:37:16 AM, you wrote:
Andrew Mather wrote:
ps: the example given at http://www.zend.com/php/internals/ makes sense, as such,
but while the first two command (phpize, ./configure, seem to work, the make command
throws errors like confetti, based on the lack of php.h, zend.h etc in an environment that
was installed 'out of the box' of Suse 9.3, rather than to the bespoke 'we can rebuild it'
requirements of the example.Making such an example compile and run as a dynamically loadable module in the
described environment would be my goal, allowing me to extend it as required later.
Perhaps you didn't install the -dev package in SUSE? I know nothing
about SUSE and how they chose to package PHP, but if you installed PHP
from our sources, it would have installed those files. I am sure SUSE
has those hidden away somewhere.
They have and there is no need to rebuild php completley, you can build
extensions standalone, only most developers prepare integrated builds in
the beginning.
For some info: http://talks.marcus-boerger.de you'll find what you want.
Best regards,
Marcus