On 11/30/2014 04:31 PM, Fraser Adams wrote:
Now I'm thinking that make install hasn't pulled all of the necessary
files into /usr/local/lib/proton/bindings/python the reason I'm thinking
that is when I tried running
source config.sh
I noticed that the PYTHONPATH it created looked like
PYTHONPATH=/home/fadams/qpid/git/qpid-proton/tests/python:/home/fadams/qpid/git/qpid-proton/proton-c/bindings/python:/home/fadams/qpid/git/qpid-proton/build/proton-c/bindings/python
and this *does* appear to work, the significant bit seems to be the
/home/fadams/qpid/git/qpid-proton/proton-c/bindings/python bit, because
when I tried:
PYTHONPATH=/home/fadams/qpid/git/qpid-proton/proton-c/bindings/python:/usr/local/lib/proton/bindings/python
that worked too.
So I'm thinking that the directory proton and its contents in
qpid-proton/proton-c/bindings/python need to be copied to
/usr/local/lib/proton/bindings/python
as part of the make install process too.
Does that seem about right?
The install loses any necessary structure, specifically now the 'proton'
sub directory for the new package. I hit the same thing and committed a
fix to the examples branch:
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=805cd17e360fd77eab29d60955a2193c7e7f0635
