Building of the liblouis dll and lib is integrated into NVDA's build process.
It even gets the correct version from configure.ac, etc. I also did the same
for liblouisutdml, though we don't currently use that code. This is done with
scons. I'm not sure whether there are issues that would prevent this from being
done for the tools as well or how hard this will be. The main problem is that
I'm pretty much always snowed under lately and don't have much time to look at
this. Also, liblouis* has settled on autotools and there seemed to be a lot of
(understandable) resistance to changing this.
Sent from a mobile device
On 8 Sep 2015, at 7:49 PM, Arend Arends <mada73bg@xxxxxxxxxx> wrote:
Hi Paul,
Thank you for the offer.
The original question of Christian was:
(...) My question hence: is anyone even using these binaries and are they
useful? If yes then I'm looking for a way to off-load this job. Maybe
someone trusted in the community could take over this job or help me set
up some automation that could build the binaries automatically.
For version 2.6.4 he added liblouis-2.6.4-w64-mingw32.zip and for earlier
versions liblouis-2.6.3-mingw32msvc.zip and the like.
So far few people have actually answered this question. Maybe your offer goes
in that direction.
To be complete one should probably produce 32 and 64 bit versions that work
for mingw and for msvc. To be complete there should be versions for 16 bit
and 32 bit Unicode, so possibly 8 versions.
I use MSVC 32 bit and 16 bit Unicode and had no trouble building this using
the instructions in readme.windows (note that instead of liblouis-2.dll/lib
the system now produces liblouis.dll/lib), only it is some work to select the
paths in Command Line to set the environment variables and produce the
build. In the past I have made a project file to build liblouis automatically
from MSVC, but for liblouisutdml this was not so easy, so I still do it as
described in libluisutdml-x.x.x\readme.windows (more or less, since there are
some steps that are not in that file like setting the environment variables).
This build process is independent from the actual project where I use
liblouis and liblouisutdml, so I don’t know whether it is useful to send
those projects.
In addition please note that I make a few changes in the files, especially
the logging part is not fully compatible with MSVC it seems. I have reported
about that but did not actually put the changes into github because of lack
of time.
Attached is the version of logging.c that I used for liblouis-2.6.3.
Arend
From: Paul Wood (Torch)
Sent: Tuesday, September 8, 2015 11:07 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Pre-built Windows binaries
Hi Guys,
One reason I've kept quiet until now is I'm quite busy, now the holiday
season is over! But also I was very interested what other, more expert,
people had to say on the Windows builds.
What I have resorted to doing is creating a Debian VM and following Bert's
Dockerfile to the letter and that has been generally successful. As a windows
guy and I presume the majority of those who want a windows build are windows
guys, then we want to use windows to build. If I may ask help from Arend to
send me a zip of his Visual Studio (VS) projects that would enable me to
build in windows then I would be happy to commit to building the dlls and
libs, but I would no doubt have to pester the 'experts' from time to time if
there are any issues I can't resolve!
Please let me know your views!
As far as MacOS is concerned I have no Macs and even less understanding of
what is needed etc. so I'm afraid cannot help with that side of the world.
HTH
Paul
On 07/09/2015 23:39, James Teh wrote:
On 8/09/2015 1:50 AM, Gregory Kearney wrote:
If we can not have pre-build binaries, a serious shortcoming that will
forever limit liblouis usefulness in my opinion
can we at an absolute minimum insure we release liblouis, and moreLast time I checked, a great deal of software out there has dependencies.
important libLouisutdml, in distributions which we know can be configured
(./configure), build (make) and installed (make install) cleanly on every
platform without demanding that the user have all manner of odd packages
installed?
That's the nature of libraries.
For what it's worth, we will never have a nice build system on Windows until
liblouis stops using autotools. Since that will probably never happen, we
will probably never have a nice build system on Windows. :)
Jamie
--
Paul Wood, Chief Technical Officer
Torch Trust
Torch House, Torch Way,
Market Harborough, Leics. LE16 9HL, UK
Direct Line: +44(0)1858 438269
Tel: +44(0)1858 438260, Fax: +44(0)1858 438275
Email: paulw@xxxxxxxxxxxxxx
Website: www.torchtrust.org
____________________________________________________
Chief Executive: Dr Gordon Temple
Charity No. 1095904
Privileged/Confidential Information may be contained in this message.
If you are not the intended recipient please destroy this message
and kindly notify the sender by reply email. The computer from which
this mail originates is equipped with virus screening software.
However Torch Trust cannot guarantee that the mail and its attachments
are free from virus infection.
<logging.c>
