Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58322
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
Received-SPF: pass (google.com: domain of hannes.magnusson@gmail.com designates 10.101.176.6 as permitted sender) client-ip=10.101.176.6;
MIME-Version: 1.0
In-Reply-To: <1330501833.99416.YahooMailNeo@web29504.mail.ird.yahoo.com>
References: <1330464316.3034.YahooMailNeo@web29505.mail.ird.yahoo.com>
	<4F4D4E79.1080602@lerdorf.com>
	<CAKxcST8H438=ymrW=ppBFjf=fXxaSOjAMeAkcsC3TuyhriHQow@mail.gmail.com>
	<1330501833.99416.YahooMailNeo@web29504.mail.ird.yahoo.com>
Date: Wed, 29 Feb 2012 08:59:02 +0100
Message-ID: <CADNQb0U6jksf6ZbfMnJWZqkXnNUKyWsCS-MfqVu1rM=CFq1JNA@mail.gmail.com>
To: Christian Ferrari <camauz@yahoo.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Newbie: issues developing a new extension
From: hannes.magnusson@gmail.com (Hannes Magnusson)

On Wed, Feb 29, 2012 at 08:50, Christian Ferrari <camauz@yahoo.com> wrote:
>>> =C2=A0> Dear all,
>
>>> =C2=A0> I'm asking your help because I'm not able to solve an issue
>> probably
>>> =C2=A0related to some foolish mistake I have not yet discovered.
>>> =C2=A0> I'm trying to develop an experimental extension to interface LI=
XA
>>> =C2=A0library (http:/lixa.sourceforge.net/).
>>> =C2=A0>
>>> =C2=A0> I have created the basic stuff (config.m4, lixa.c, php_lixa.h a=
nd so
>> on).
>>> =C2=A0>
>>> =C2=A0> If I use this sequence from the ext/lixa directory:
>>> =C2=A0>
>>> =C2=A0> /opt/php/bin/phpize
>>> =C2=A0> ./configure --help
>>> =C2=A0>
>>> =C2=A0> I can see the lixa extension is available:
>>> =C2=A0>
>>> =C2=A0> [...]
>>> =C2=A0> Optional Packages:
>>> =C2=A0>=C2=A0 =C2=A0--with-PACKAGE[=3DARG]=C2=A0 =C2=A0 use PACKAGE [AR=
G=3Dyes]
>>> =C2=A0>=C2=A0 =C2=A0--without-PACKAGE=C2=A0 =C2=A0 =C2=A0 =C2=A0do not =
use PACKAGE (same as
>> --with-PACKAGE=3Dno)
>>> =C2=A0>=C2=A0 =C2=A0--with-libdir=3DNAME=C2=A0 =C2=A0 =C2=A0 Look for l=
ibraries in .../NAME rather than
>>> =C2=A0.../lib
>>> =C2=A0>=C2=A0 =C2=A0--with-php-config=3DPATH=C2=A0 Path to php-config p=
hp-config
>>> =C2=A0>=C2=A0 =C2=A0--with-lixa=3DFILE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Inclu=
de LIXA support. File is the path to
>>> =C2=A0lixa-config
>>> =C2=A0>
>>> =C2=A0> [...]
>>> =C2=A0>
>>> =C2=A0> and I can compile with:
>>> =C2=A0>
>>> =C2=A0> ./configure --with-lixa=3D/opt/lixa/bin/lixa-config
>>> =C2=A0--with-php-config=3D/opt/php/bin/php-config
>>> =C2=A0>
>>> =C2=A0> the build process runs as expected and the extension is availab=
le
>> after
>>> =C2=A0an addition to php.ini (extension=3D[...]/ext/lixa/modules/lixa.s=
o).
>>>
>>> =C2=A0Great, you are done. Why do you want to go any further than this?=
 You
>>> =C2=A0built your extension and it is available from PHP exactly like an=
y pecl
>>> =C2=A0extension.
>>>
>>
>> and if you're using apache, reboot it and check your phpinfo() page for
>> your extension.
>> if you're connected up via the command line you can run "php -m"
>> to see if
>> your modules exists.
>>
>>
>>>
>>> =C2=A0-Rasmus
>>>
>
> Dear all,
> I would like to see my extension as any other extension, like MySQL, Post=
greSQL, Oracle and so on because:
> 1. LIXA itself is useless without those resource managers
> 2. I need to patch other extensions to implement the interfaces between L=
IXA and MySQL/PostgreSQL/Oracle.
> What's the difference between an "internal" extension (like
> MySQL/PostgreSQL/Oracle) and an "external" extension as the one I
> produced?
> Thanks in advance, your help is precious.


The PHP source archive bundles several extensions under the ext/
directory, these are the extensions are listed when you run
./configure --help

I don't understand why you want your extension to show up there, but
to do so you have to place your extension in that folder and run
./buildconf --force
PHP will not automatically scan your filesystem for possible extension
directories to list them under ./configure
I'm sure you have seen, and used, http://pecl.php.net - these
extensions don't show up when you build PHP.

The standard way to build "external" extensions however is to use
pecl, or manually build them as shared modules (as you did first).


-Hannes