Hi Arend,
The problem You mentioned is real.
Apart from the warnings I listed earlier, the manual build process seemed okay
but it did not produce any exe files.
So far, I was unable to figure out how to compile the executables from the
command prompt. Without them, it seems a bit difficult to test the resulted
liblouis.dll.
Just for a try, I took the .exe files from the bin folder of
liblouis-3.1.0-mingw32msvc.zip and attempted to run lou_checktables.exe.
The immediate result was a popup window telling something like this:
The procedure lou_free@0 entry point cannot be found in the DLL.
Both the .exe and liblouis.dll built by me are 32-bit PE versions (the 32-bit
version of the msvc and probably that of the entire vs is installed here).
What am I doing wrong? What do You think I should do to get past this stage?
Thanks a lot in advance.
Best Regards, Norbert.
From: Arend Arends
Sent: Thursday, March 16, 2017 12:44 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Build questions
Hi Norbert,
You can investigate the warning message in more detail in the source code if
you are interested.
You can make sure that the rebuild is complete by removing the files that are
produced by the compilation, especially the obj files.
Arend
From: Norbert Markus
Sent: Thursday, March 16, 2017 12:13 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Build questions
Dear Arend,
Thanks a lot for Your confirmation. I also hope these warnings indicate no
crucial problems but because they mentioned possible loss of precision due to
data type mismatches, I got a bit alarmed.
By the way, do You happen to know how to compile in Windows the executables for
a freshly built liblouis.dll?
Thanks in advance: Norbert.
From: Arend Arends
Sent: Tuesday, March 14, 2017 4:13 PM
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?