----- Original Message -----
> From: "Gordon Sim" <[email protected]>
> To: [email protected]
> Sent: Thursday, September 1, 2016 8:32:15 AM
> Subject: Re: Python support for AMQP 1.0?
>
> On 01/09/16 09:29, Volker Diels-Grabsch wrote:
> > So I have to switch from a pure-Python implementation to a C library
> > with Python wrapper. This is inconvenient for deployment, but not a
> > show stopper for me.
> >
> > I compiled qpid-proton on my own, where some questions arose:
> >
> > 1) Is it possible to build just the Python part? (plus C library, of
> > course)
>
> Yes, you can turn off other languages with cmake options
> (-DBUILD_CPP=OFF -DBUILD_PERL=OFF -DBUILD_RUBY=OFF -DBUILD_JAVA=OFF
> -DBUILD_GO=OFF -DBUILD_JAVASCRIPT=OFF -DBUILD_PHP=OFF)
>
> You can see all the options with ccmake, and edit them interactively.
>
> > 2) If not, is there at least a way to build just proton-c without proton-j?
> >
> > 3) Is it possible to link the _cproton.so wrapper and the libqpid-proton.so
> > library into a single *.so file?
>
> No, I don't believe it is.
>
>
Actually, this is exactly what the Pypi setup package script does if the python
libs are not installed. The resultant _cproton.so contains all the proton-c
bits necessary, there are no external deps on libqpid-proton.so:
[kgiusti@localhost site-packages (master)]$ ls -l *cproton*
-rw-rw-r--. 1 kgiusti kgiusti 117534 Aug 30 08:53 cproton.py
-rw-rw-r--. 1 kgiusti kgiusti 196120 Aug 30 08:53 cproton.pyc
-rwxrwxr-x. 1 kgiusti kgiusti 2917992 Aug 30 08:53 _cproton.so
[kgiusti@localhost site-packages (master)]$ ldd _cproton.so
linux-vdso.so.1 (0x00007ffe01df2000)
libssl.so.10 => /lib64/libssl.so.10 (0x00007f30a6052000)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f30a5bf2000)
libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f30a59d4000)
libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f30a5605000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f30a53e7000)
libc.so.6 => /lib64/libc.so.6 (0x00007f30a5025000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f30a4dd7000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f30a4aef000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f30a48ea000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f30a46b8000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f30a44b4000)
libz.so.1 => /lib64/libz.so.1 (0x00007f30a429d000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f30a4082000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f30a3e4c000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007f30a3c48000)
libm.so.6 => /lib64/libm.so.6 (0x00007f30a3946000)
/lib64/ld-linux-x86-64.so.2 (0x0000562d14006000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f30a3737000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f30a3532000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007f30a332f000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f30a310b000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f30a2e98000)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
