Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21836
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Status: good
DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws;
	s=test; d=omniti.com;
	h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=nwIK2rNWyzptue/4h2vzNiqFTEUKzTMPmCub1abqQzlBTsXyukTX6j8Eux52fA0p
	/GkG9OhQrdtqKCqDm4bIp4OODgqrfWubZ06NZc6PSUyIiEMA2Um0279e5k66Og9M
Message-ID: <43ECB7E8.2000009@omniti.com>
Date: Fri, 10 Feb 2006 10:57:28 -0500
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Andrew Mather <an.dromeda@btconnect.com>
CC: internals@lists.php.net
References: <00d601c62e50$2b3f7c00$ca5f8a51@VaioCen>
In-Reply-To: <00d601c62e50$2b3f7c00$ca5f8a51@VaioCen>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Dead C Scrolls - Missing Code for Writing New Extensions
	without recompiling PHP
From: george@omniti.com (George Schlossnagle)

Andrew Mather wrote:

>i)    a walkthrough of the exact steps + sample code to write an extension without
>       requiring re-compilation of Php and without access to Php source code
>  
>
>ii)   as above but with access to Php source code
>  
>
You're clearly missing the -devel RPM that installs the necessary header 
files to allow you to build extensions outside of a source tree.  That 
devel rpm will install the phpize and php-config executables, and a set 
of headers under the appropriate destination for your distro (I'm not a 
SuSE user, but I would expect them to be either under /usr/include/php 
or /usr/local/include/php).  If you don't have these then you need to 
get the RPM that provides them (php-devel or something along those 
lines) before you can move forward.  Look at practically any extension 
in PECL and read it's INSTALL instructions.  For instance, look at APC 
and read it's INSTALL file.  Again, without the -devel RPM that provides 
your necessary headers you will be up th creek.

>iii)  as above (either i or ii) but with instructions to allow the project to be initiated
>      and compiled within the KDE development environment
>  
>
That shouldn't make any difference.

George