On 13/11/2010 8:05 PM, Dr.Leo wrote:
Well, you need to run ./configure, yes. However, you also need this (and other build tools) to build the liblouis dll, which is part of the bindings in the sense that the bindings depend on it. The bindings are dependent on a specific version of the dll. In addition, other operating systems obviously require their own build of the library. This makes it impossible to distribute liblouis using standard Python packaging techniques.My understanding is that one needs autotools to generate the Python bindings from the __init__.py.in file in the svn repo. Is my understanding correct?
To further complicate matters, there is no standard location in which to place the liblouis tables in Windows. The dll is built with the default location specified at compile time. You can override this, of course, but it means you can never just write "table-filename"; you must always provide the full path or set an environment variable. The dll must also be placed in system32 or similar if you want Python to be able to find it.
All of this said, you can grab the Windows Python bindings as packaged for NVDA from here:
http://www.nvda-project.org/3rdParty/liblouis-python-win_2.1.1.zipI've avoided making these official due to the above issues and potential confusion that might result.
Jamie -- James Teh Vice President NV Access Inc, ABN 61773362390 Email: jamie@xxxxxxxxxxxx Web site: http://www.nvaccess.org/ For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com