[liblouis-liblouisxml] Re: Pre-built Windows binaries

  • From: Davy Kager <DavyKager@xxxxxxxxxx>
  • To: "'liblouis-liblouisxml@xxxxxxxxxxxxx'" <liblouis-liblouisxml@xxxxxxxxxxxxx>
  • Date: Mon, 7 Sep 2015 07:13:20 +0000

Bert, is there anything you do not have a script for? :)

My feeling is that hte Windows builds should be done using MSVC if possible.
Having a Microsoft-compatible .lib-file sounds very useful.

-----Oorspronkelijk bericht-----
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Bert Frees
Verzonden: donderdag 3 september 2015 18:13
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx
Onderwerp: [liblouis-liblouisxml] Re: Pre-built Windows binaries

I have a script for building liblouis on all platform. It produces both 32 and
64 bit version for Windows. Mingw doesn't create a .lib file, but it does
create a .dll.a file, which can be used for linked in the mingw world. Don't
know how useful that is for you.

See the repository called liblouis/liblouis-nar for more information. Note that
the binaries are packaged in NAR format, which is basically a ZIP.


Arend Arends writes:

Hi Christian,

I have so far downloaded several versions of the mingw32msvc versions,
but not the latest version. I have studied the contents, but after all
I most of the time used the version that I compiled myself with MSVC.
One reason is that I need that version to build LibLouisutdml. Another
reason is that I was not sure about the result. When I compile with
MSVC I need to make some changes.
It is not quite clear whether the mingw32 version compiles for 16 or
32 bits characters input/output. I assume 16 bits because of the
definition in
liblouis.h:
#define widechar unsigned short int

Further there is no lib file included, which is necessary for linking
the dll.

I normally do not use the tools because I am generally not involved in
producing tables. I hate to use command line tools. It would probably
be better if I had a set of batch files available so I do not have to
do a lot of typing before I can start running the tools (this goes
also for the compilation process).

Ideally I would like to get compiled versions for both liblouis and
liblouisutdml with the necessary header files and lib files.
Is the current compiled version useful? Yes it still is, if one has
problems with doing the compilation oneself or for comparison.

I would like to dive into the matter of making these things more
automatic, but thusfar I lacked the time or energy. It would also
require some knowledge of the other build systems.

Best regards,

Arend Arends

-----Oorspronkelijk bericht-----
From: Christian Egli
Sent: Thursday, September 3, 2015 4:55 PM
To: liblouis-liblouisxml
Subject: [liblouis-liblouisxml] Pre-built Windows binaries

Hi all

For the last few releases I not only packed up a tar ball of the
source code, but I also built a zip file containing a dll and some exe
files of the tools using mingw.

Now I changed machines and my mingw infrastructure has changed and I
only seem to be able to build 64bit versions. That is what I uploaded
for the 2.6.4 release. But since I do not use Windows I have no way of
testing these binaries.

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.

Thanks
Christian

For a description of the software, to download it and links to project pages go
to http://liblouis.org
DISCLAIMER:
De informatie verzonden met dit e-mail bericht is uitsluitend bestemd voor de
geadresseerde. Indien u niet de beoogde geadresseerde bent, verzoeken wij u
vriendelijk dit aan de afzender te melden (of via:
info@xxxxxxxxxx<mailto:info@xxxxxxxxxx>) en het origineel en eventuele kopieën
te verwijderen.

The information sent in this e-mail is solely intended for the individual or
company to whom it is addressed. If you received this message in error, please
notify the sender immediately (or mail to
info@xxxxxxxxxx<mailto:info@xxxxxxxxxx>) and delete the original message and
possible copies.

Other related posts: