[liblouis-liblouisxml] Re: MacOS workflow for Braille
- From: David Sweetman <david@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Wed, 14 May 2014 13:01:11 -0700
I think you likely won’t want to have end-users building the library from
source — though it may be simple to make a homebrew or macports installer (and
it looks like a macports installer does exist, but it’s outdated at version
2.1.1), that's still probably asking a lot of the average user.
I’ve never distributed a tool like this so I’m hazy on exactly what is required
— but for liblouis, looking at the __init__.py created by python/setup.py, it
appears the python binding makes use of the dynamic library ‘liblouis.2.dylib’,
(line 65). So potentially all you need to do is somehow include that dylib for
the python bindings to work. From the directory where you’ve build liblouis, if
you run:
find . | grep dylib
It should return two results in the hidden .libs folder:
./liblouis/.libs/liblouis.2.dylib
./liblouis/.libs/liblouis.dylib
According to the README in the liblouis python directory, that dylib is
expected to be in a standard install location, and I’m not really 100% clear on
what that means in context of cdll loading it in the init script. Hopefully
somebody else can advise on best-practice for what you want to do, but if you
provide a dylib to end-users, you may have to find a way to somehow either tell
python to look for the dylib where you’ve put it, or adjust __init__.py to use
the full path to the dylib you’ve provided (again, that's just a hypothesis,
it’s uncharted territory for me).
On May 14, 2014, at 10:58 AM, Greg Kearney <gkearney@xxxxxxxxx> wrote:
> OK here is what I am working on which is why I needed to get liblouis working
> in the first place.
>
> I have a system service for MacOS that will take the highlighted text and
> translate it into contracted UEBC Braille and replace the selected text with
> this translation. This is to be used mostly by sign writing companies, Think
> of selected the text for a sign and getting back the braille.
>
> Now for this to work I need to have a method of installing not only the
> service but also libouis as well as to make sure the python binding get
> activates, the translation is done in a python script. So now what I need is
> a complete list of where everything get put when we do make install so that I
> can go and copy all these files and build an installer to put everything
> where it needs to be, run the python setup.py script and have everything in
> place for the service.
>
> There is no way that any fellow in a sign shop or consumer end user of this
> will ever understand the whole configure.make/make install process. Further
> most will not have the developer tools installed to do so.
>
> So can someone provide me with the paths and names of everything that
> liblouis installs so that I can make up a way to install all of this?
>
> Thanks
>
>
> Commonwealth Braille & Talking Book Cooperative
> Greg Kearney, General Manager
> 605 Robson Street, Suite 850
> Vancouver BC V6B 5J3
> CANADA
> Email: info@xxxxxxxxx
>
> U.S. Address
> 21908 Almaden Av.
> Cupertino, CA 95014
> UNITED STATES
> Email: gkearney@xxxxxxxxx
>
>
>
> For a description of the software, to download it and links to
> project pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
