Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21817
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 9 Feb 2006 01:41:08 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1272469188.20060209014108@marcus-boerger.de>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Andrew Mather <an.dromeda@btconnect.com>, internals@lists.php.net
In-Reply-To: <43EA8EBC.3040902@lerdorf.com>
References: <000e01c62cfd$ef7443c0$ca5f8a51@VaioCen> <43EA8EBC.3040902@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Writing PHP extensions without re-building PHP
From: helly@php.net (Marcus Boerger)

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