[BRLTTY] Questions about brltty and Orca

[Didier Spaier]

Le 09/09/2017 à 13:16, Dave Mielke a écrit :

>> 4) In the above described context, do I need to ship brlAPI? so far
>> I target end users rather that developers, so I am considering not
>> installing it by default, but providing it as a package. What do you
>> think? Is it needed beyond developing new drivers or such use cases?
> 
> That depends on what's in your BrlAPI package. While you don't need to install 
> its headers and documentation, you do need to install its shared object (.so 
> file) and bindings (e.g. Orca uses BrlAPI's Python bindings).


So I did.
However, when I try to build Orca I get:

 
checking for a Python interpreter with version >= 3.3... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.5
checking for python3 platform... linux
checking for python3 script directory... ${prefix}/lib64/python3.5/site-packages
checking for python3 extension module directory... ${exec_prefix}/lib64/python3.5/site-packages
checking for python module gi... yes
checking for python module json... yes
checking for python module brlapi... no
checking for python module speechd... yes
checking for python module louis... yes

My guess is that it doesnt find BrlAPI's Python bindings,
because python-brlapi-0.6.6-1.x86_64.rpm ships:

/usr/lib64/python2.7/site-packages/Brlapi-0.6.6-py2.7.egg-info
/usr/lib64/pytho/usr/lib64/python2.7n2.7/site-packages/brlapi.so

and configure looks in /usr/lib64/python3.5, not /usr/lib64/python2.7

Should I just try to make symlinks or a copy, or do I need to rebuild
the Python bindings?

And in the latter case, where do I find the sources?
TIA,
Didier