[ 
https://issues.apache.org/jira/browse/PROTON-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801649#comment-13801649
 ] 

Andrew Degtyarov commented on PROTON-356:
-----------------------------------------

It's not patch but I had have working version of PHP extension under MacOS X 
10.7 and 10.8:

1. Edit proton-c/CMakeLists.txt and comment out string "set (NOBUILD_PHP ON)" 
under "if (APPLE)" block
2. cd build
3. export CC=cc # Chose LLVM compiler 
4. Execute 
    cmake -DPHP_INCLUDE_DIR=/usr/local/Cellar/php53/5.3.23/lib/php/ 
-DCMAKE_INSTALL_PREFIX=/usr/local -DPYTHON_EXECUTABLE=/usr/local/bin/python 
-DPYTHON_LIBRARY=/usr/local/Cellar/python/2.7.4/Frameworks/Python.framework/Versions/Current/lib/libpython2.7.dylib
 ..

In this line I asked to bind with brew version of Python and put cproton.php 
and proton.php into brew PHP include directory instead of /usr/share/php
5. Edit proton-c/bindings/php/CMakeFiles/cproton.dir/link.txt and replace their 
content by line
/usr/bin/cc    -bundle -Wl,-flat_namespace -Wl,-undefined -Wl,suppress  -o 
cproton.so CMakeFiles/cproton.dir/phpPHP_wrap.c.o 
../../libqpid-proton.1.0.0.dylib  /usr/lib/libssl.dylib 
/usr/lib/libcrypto.dylib 

> PHP bindings are not built on MacOS 10.8
> ----------------------------------------
>
>                 Key: PROTON-356
>                 URL: https://issues.apache.org/jira/browse/PROTON-356
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.4
>         Environment: MacOS X 10.8, Homebrew
>            Reporter: Serge Smertin
>            Priority: Critical
>
> it's not possible to build PHP extension for MacOS, as it gives linking 
> error. Relates to issue - https://issues.apache.org/jira/browse/PROTON-108, 
> which is not resolved properly. 
> Short-term viable solution:
> - Attach *.so files to this ticket for macos x exactly
> Long-term solution:
> - Make proper linking



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to