Hi Volker, I would recommend you use the python-qpid-proton package available at the pypi repository:
https://pypi.python.org/pypi/python-qpid-proton/0.14.0 The package setup script will automagically check to see if the proton-c library has been installed and will use it if available. Otherwise the setup script will pull down the necessary C files from apache.org and build and install them to your site-packages dir. This will avoid downloading the whole proton distribution and building everything - only the C stuff necessary for the python binding is built. Having said that - you'll need to have the proper build tools and libraries installed in order for this build to succeed. At a minimum you'll need SWIG, the python development libraries installed and the dev packages for whatever libs you need for proton-c (like OpenSSL or Cyrus SASL) One caveat: this build script only works on linux-based systems. It should work on other unix-y systems but hasn't seen much testing there. And windows is a no-go at this point. Of course, patches to support other platforms would be gladly accepted :) -K ----- Original Message ----- > From: "Volker Diels-Grabsch" <[email protected]> > To: [email protected] > Sent: Thursday, September 1, 2016 4:29:22 AM > Subject: Re: Python support for AMQP 1.0? > > Gordon Sim schrieb: > > On 31/08/16 18:26, Volker Diels-Grabsch wrote: > > > In other words, how is a Python program meant to communicate with an > > > AMQP 1.0 server? > [...] > > Use the proton library for python. There is an overview, a tutorial, some > > examples and an API reference of sorts: > > https://qpid.apache.org/proton/index.html. Feel free also to ask questions > > on this list. > > Thanks for the quick reply! > > 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) > > 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? > > (Rather than having _cproton.so depending on libqpid-proton.so > which has to be installed system wide or needs LD_LIBRARY_PATH > magic.) > > > Regards, > Volker > > -- > Volker Diels-Grabsch > ----<<<((()))>>>---- > > --------------------------------------------------------------------- > 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]
