pear/pecl and c-modules

From: Date: Sat, 17 Nov 2001 11:26:17 +0000
Subject: pear/pecl and c-modules
Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-2948@lists.php.net to get a copy of this message
Hi I wrote my very first php-extension yesterday (a svg2png-converter with the help of librsvg from gnome, more about that later). I'd like to put that into PEAR, but I have some questions about that. There's PECL, which is for traditional php-extension, so I think my extension will better fit there than into the main PEAR-Tree (but if it's more appropriate, i can rewrite the functions to the PEAR-Standards, it's not much there at the moment). Is there any other difference between PECL and PEAR than the coding standards? and where should new extensions go in principal? Second. How does the PEAR::Installer handle extensions? Does it just copy the source-code into php4/ext/ and then i have to recompile my main php, or does it make a selfcontained extension? or do i have to do all by myself (copying or compiling) and the PEAR::Installer just gets the source? How does a package.xml to look like for an extensio? Jo, that's it for the moment. More questions will certainly follow:) and if anyone is interested in having a look into the extension, see http://cvs.bitflux.ch/index.cgi/pearlib/rsvg/ (but it needs the alpha gnome2 stuff for running, since librsvg from gnome1.4 runs with libxml1 and i couldn't bring that together with domxml which needs libxml2, anyone having an idea, how this could be done nevertheless?) Be warned, it's very experimental... so long chregu

« previous php.pear.dev (#2948) next »