Re: debugging PECL extension with eclipse or other IDE
| From: | j adams | Date: | Mon, 18 Apr 2011 18:18:56 +0000 |
| Subject: | Re: debugging PECL extension with eclipse or other IDE | ||
| References: | 1 2 3 4 5 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-8118@lists.php.net to get a copy of this message | ||
Thanks Christopher for that suggestion. I didn't see a "buildconfig"
but I do in fact see a buildconf so tried that and it complains about
VCS and doesn't clean:
jaith@Ubuntu-64bit:~/src/php-5.3.6$ ./buildconf --force
Forcing buildconf
buildconf: checking installation...
buildconf: autoconf version 2.67 (ok)
buildconf: Your version of autoconf likely contains buggy cache code.
Running vcsclean for you.
To avoid this, install autoconf-2.13.
Can't figure out your VCS, not cleaning.
Now my configure script won't run.
I googled around for a solution and the recommendation seems to be to
rollback autconf from the current 2.67 to the much older 2.13. Any
thoughts on how to get buildconf to run correctly?
On Mon, Apr 18, 2011 at 11:01 AM, Christopher Jones
<christopher.jones@oracle.com> wrote:
>
> On 04/18/2011 10:55 AM, j adams wrote:
>
>> I cannot, however, build PHP with --enable-amf. Here's my configure
>> command:
>> ./configure --with-apxs2=/usr/bin/apxs2 --with-mysql --enable-exif
>> --enable-ftp --enable-mbstring --with-mysqli --with-pdo-mysql
>> --enable-soap --enable-sockets --enable-wddx --with-xmlrpc
>> --enable-zip --with-openssl --with-curl --with-gd --with-mcrypt
>> --with-jpeg-dir=/usr/lib --enable-pcntl --prefix=/usr --enable-debug
>> --enable-amf
>>
>> The result says --enable-amf is not a recognized option.
>>
>> Notice: Following unknown configure options were used:
>> --enable-amf
>>
>> Building the amf extension all by itself in its own dir manually via
>> cli works just fine, creating amf.so. The main problem I face is how
>> to get this PHP project to either build with amf built-in or to load
>> amf.so dynamically by parsing a PHP.ini file. I think the ideal
>> situation would be one wherein I can build *just* my extension from
>> within the GUI and then call PHP with a parameter specifying a php.ini
>> which causes it to load my amf.so file as a dynamic extension.
>
> After moving the AMF code to <yourphpdir>/ext/amf you need to rebuild
> PHP's 'configure' script:
>
> cd <yourphpdir>
> rm -rf config.cache autom4te.*
> ./buildconfig --force
>
> and then 'configure' should recognize --enable-amf
>
> Chris
>
> --
> Email: christopher.jones@oracle.com
> Tel: +1 650 506 8630
> Blog: http://blogs.oracle.com/opal/
>