On 02/28/2012 01:25 PM, Christian Ferrari wrote: > Dear all, > I'm asking your help because I'm not able to solve an issue probably related > to some foolish mistake I have not yet discovered. > I'm trying to develop an experimental extension to interface LIXA library > (http:/lixa.sourceforge.net/). > > I have created the basic stuff (config.m4, lixa.c, php_lixa.h and so on). > > If I use this sequence from the ext/lixa directory: > > /opt/php/bin/phpize > ./configure --help > > I can see the lixa extension is available: > > [...] > Optional Packages: > --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] > --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) > --with-libdir=NAME Look for libraries in .../NAME rather than .../lib > --with-php-config=PATH Path to php-config php-config > --with-lixa=FILE Include LIXA support. File is the path to > lixa-config > > [...] > > and I can compile with: > > ./configure --with-lixa=/opt/lixa/bin/lixa-config > --with-php-config=/opt/php/bin/php-config > > the build process runs as expected and the extension is available after an > addition to php.ini (extension=[...]/ext/lixa/modules/lixa.so).
Great, you are done. Why do you want to go any further than this? You built your extension and it is available from PHP exactly like any pecl extension. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php