sikuli-driver team mailing list archive

[RaiMan <question227414@xxxxxxxxxxxxxxxxxxxxx>]

Question #227414 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/227414

RaiMan posted a new comment:
Sorry, I do not have Tesseract libs 64-Bit, built with VS.

In Feb 2010 I succeeded to build a 64-Bit Sikuli (from faq 1453):

A 64-Bit version of sikuli-script.jar and Sikuli-IDE (X-1.0rc2) is
running fully 64-Bit now (Java 64-Bit only, OpenCV2.2 and tesseract2.04
both 64Bit).

Tools used:
-- Visual C++ 2010 Express (VC)
-- Windows SDK 7.1 / .Net 4
-- cmake2.8(32Bit) running from a commandline prepared with SetEnv.cmd from the SDK
-- swig 2.01(32Bit)
-- I used cmake -G "Visual Studio 10 Win64" to generate .vcxproj projectfiles for VC
-- I processed all builds in the VC gui with Release/x64
-- nmake did not work for me (linker problems)

I had to fix/hack the following:
Source --- tesseract/scrollview.cpp: some compile errors that could be fixed using the recommendation (reinterpret_cast)
VC --- in VC project settings I had to switch in the configuration settings the platformtoolset to "Windows7.1SDK" manually for each build, because VC is not taking this setting from environment automatically (otherwise the linker would not find the 64-Bit versions of standard libs)
VC --- when opening a cmake generated .vcxproj, the target is Debug, though environment tells Release - has to be manually switched
VC --- VC generates a Release and a Debug folder in the relevant target folders - I had to fix the dll-to-jar copy
Cmake --- the javah.exe was not found by cmake, though path was set - put absolute path into cmakelist

But I never tried it again.
With the new version (https://github.com/RaiMan/Sikuli12.11) I am using mingw.

You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.