Hi Anders,
The reason is that actually I'll need to use liblouisutdml.dll. I was unable to
find a pre-built dll version for Windows. If You are aware of any site from
which a recent liblouisutdml.dll can be downloaded, this would save me from
building it manually.
But if this is a necessary step, it seems, liblouis.lib is required for
building liblouisutdml.dll, and I could not find liblouis.lib for download.
Thus I had to build it manually to obtain the lib file.
I hope my explanation makes at least some sense.
Best Regards, Norbert.
From: Anders Boholdt-Petersen
Sent: Tuesday, March 14, 2017 5:08 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] SV: Re: Build questions
Hi
Why you manually should compile Liblouis, e.g. on Windows before you can use
the program?
I ask you since that you normaly not first must compile a program to Windows,
e.g. a screen reader, before you could install it.
Thanks for the answer.
Regards,
Anders
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] På vegne af Arend Arends
Sendt: March 14, 2017 16:14
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Build questions
Hi Norbert,
I recently compiled Liblouis in roughly the same way, with the same compiler
for Windows and I probably got similar warning errors (I don’t remember exactly
and I thought I made a copy or a photograph of the screen, but I cannot find it
right now).
In addition I got a link error because a new component was not added yet in the
Windows version, but that has been corrected in the meantime by Christian.
So somebody could try to resolve these warning errors, but I don’t think it is
something to worry about right now. When you recompile, you have to make sure
it is a full recompilation because the test on new components seems to be
incomplete.
Arend Arends
From: Norbert Markus
Sent: Tuesday, March 14, 2017 3:22 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Build questions
Dear Christian and All,
Here are my questions:
- I have done the things listed below on a Windows 7 64-bit system with MS
Visual Studio Community 2015 installed.
- I've visited the download page of the liblouis.org site, and in the
"up-to-date versions" section, clicked
https://github.com/liblouis/liblouis.git. There I clicked "Download zip" and ;
unpacked the archive into a folder on a dos-compatible path.
- Opened a Developer Command Prompt for VS 2015 offered in Visual Studio's
start menu folder and changed to the windows subfolder of the recently unpacked
zip: C:\liblouis31\windows.
- Then I issued the command: nmake /f Makefile.nmake
- It seems to have built liblouis.dll and liblouis.lib but produced a bunch of
warnings along the way. The output is as follows:
cl.exe /nologo /O2 /W3 /c -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
/Iinclude /DWIDECHAR_TYPE="unsigned short int" /DUNICODEBITS=16
..\liblouis\compileTranslationTable.c
compileTranslationTable.c
..\liblouis\compileTranslationTable.c(4756): warning C4267: '=': conversion
from 'size_t' to 'short', possible loss of data
cl.exe /nologo /O2 /W3 /c -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
/Iinclude /DWIDECHAR_TYPE="unsigned short int" /DUNICODEBITS=16
..\liblouis\lou_translateString.c
lou_translateString.c
cl.exe /nologo /O2 /W3 /c -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
/Iinclude /DWIDECHAR_TYPE="unsigned short int" /DUNICODEBITS=16
..\liblouis\lou_backTranslateString.c
lou_backTranslateString.c
cl.exe /nologo /O2 /W3 /c -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
/Iinclude /DWIDECHAR_TYPE="unsigned short int" /DUNICODEBITS=16
..\liblouis\wrappers.c
wrappers.c
cl.exe /nologo /O2 /W3 /c -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
/Iinclude /DWIDECHAR_TYPE="unsigned short int" /DUNICODEBITS=16
..\liblouis\logging.c
logging.c
lib /nologo compileTranslationTable.obj lou_translateString.obj
lou_backTranslateString.obj wrappers.obj logging.obj /out:liblouis.lib
link /dll /nologo /DEF:liblouis.def /OUT:liblouis.dll
compileTranslationTable.obj lou_translateString.obj lou_backTranslateString.obj
wrappers.obj logging.obj
Creating library liblouis.lib and object liblouis.exp
My question is whether these warnings indicate something inappropriate that
needs to be fixed or are normal and known to You and can be ignored?
Will they in any way affect the performance of liblouis.dll or
liblouisutdml.dll based on this build of liblouis.dll?
Thanks a lot for Your help in advance.
Best Regards, Norbert.
From: Christian Egli
Sent: Monday, March 13, 2017 10:34 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Build questions
On 03/13/2017 07:20 AM, Norbert Markus wrote:
Is it allowed to post here questions about building liblouis.dll and
liblouisutdml.dll in Windows?