#4 pyindi std:string and raspbian issues

[Georg Viehoever]

Using pyindi with Python3.4 and handcompiled libindi on raspbian jessie on a raspberrypi. Problems I encountered:
setup.cfg: needed to add /usr/local/include/libindi to include paths, and option swig to advertise swig3.0 as the appropriate swig compiler (swig would be 2.x). File now looks like this:
[build_ext]
swig=/usr/bin/swig3.0
swig_opts = -v -Wall -c++ -threads -I/usr/include -I/usr/include/libindi -I/usr/local/include/libindi
include_dirs = /usr/include:/usr/include/libindi:/usr/local/include/libindi
...

setup.py: add /usr/local/lib:
...
libindisearchpaths=['/usr/lib/'+march, '/usr/lib', '/usr/lib64', '/lib', '/lib64','/usr/local/lib']
...

indipythonclient.i: add std_string.i, otherwise device.getmessage(i) would not work:
...
%include "std_except.i"
%include "std_string.i"
...

Thanks for your work!

Georg

[geehalel]

Hi,
Sorry for this very late answer, Sourceforge did not send me an email concerning this issue and I don't come here very often. By the way I just put your corrections in the release 0.2.3, but I choose to not force the swig executable to be /usr/bin/swig3.0 as this depends on distributions (there is only /usr/bin/swig on Fedora for instance).
Thanks for reporting!
Jean-Luc.