If you run cmake this way you can build the minimal code needed for just
the proton library and its python bindings:

cmake -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_PYTHON=ON -DBUILD_PHP=OFF
-DBUILD_PERL=OFF -DBUILD_RUBY=OFF <path_to_src_tree>

A quick test on my system shows that a make install based on the above
build works out to about 1.4MB. Stripping out header files and some package
config stuff would get you down to about 1.2MB if you want to go super
barebones.

--Rafael

On Tue, Jan 15, 2013 at 5:38 PM, Ted Ross <tr...@redhat.com> wrote:

> Taylor,
>
> You need the following files:
>
>     proton.py          (from proton-c/bindings/python)
>     cproton.py         (from $BUILD/bindings/python)
>     _cproton.so        (from $BUILD/bindings/python)
>     libqpid-proton.so  (from $BUILD)
>
> -Ted
>
>
>
> On 01/15/2013 03:35 PM, Eagy, Taylor wrote:
>
>> Ted,
>>
>>
>>
>> Proton is more lightweight and the systems that it runs on won't have
>> Java installed. While I would prefer a more Pythonic portable solution, as
>> long as Proton-c builds within 5MB, then it should work. However, I'm
>> getting a bunch of undefined reference messages from pythonPYTHON_wrap.c
>> when trying to make install it. So if I just want to use the p2p messaging
>> between Python processes, what are the minimum amount of files that I need
>> to create a Python queue server to handle the queues between processes?
>> (i.e. proton.py, cproton.py, etc)
>>
>>
>>
>> Thanks,
>>
>> Taylor
>>
>>
>>

Reply via email to