You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "David Reiss (JIRA)" <ji...@apache.org> on 2010/08/16 22:29:29 UTC

[jira] Commented: (THRIFT-854) Provide configure option and make rules to build/install php extension

    [ https://issues.apache.org/jira/browse/THRIFT-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899075#action_12899075 ] 

David Reiss commented on THRIFT-854:
------------------------------------

I don't think putting phpize in bootstrap is good because we don't want people to run that on release tarballs.  Is there any way to move that to configure or make?

In general, I found that trying to cram other build systems into our autoconf/automake setup leads to trouble and people have better luck running ant/setup.py/gem/phpize directly.  You guys build RPMs, right?  Would you be amenable to putting these commands in contrib/thrift.spec instead?

> Provide configure option and make rules to build/install php extension
> ----------------------------------------------------------------------
>
>                 Key: THRIFT-854
>                 URL: https://issues.apache.org/jira/browse/THRIFT-854
>             Project: Thrift
>          Issue Type: Improvement
>    Affects Versions: 0.5
>            Reporter: Anthony Molinaro
>         Attachments: php-ext.patch, thrift_protocol.ini
>
>
> I like to build and install the php extension at the same time I build the php and other thrift artifacts.  The attached path adds the necessary logic to build and install the extension to work on redhat/centos/fedora machines.
> configure has a new option --with-php_extension=yes which will enable the compilation/installation of the extension, along with an environment variable 
> PHP_CONFIG_PREFIX which controls where the .ini file for enabling the extension is installed.  The one requirement for this to work is the person creating builds must have phpize installed (this prepares the autoconf artifacts to be appropriately added to the distribution).  On Centos/Redhat/Fedora this is in the php-devel package.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.