sikuli-driver team mailing list archive

[RaiMan <question205842@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
Since you have a standard setup in your DevMachine, this does not make
any problems, as long as the Sikuli/libs folder is in the Path at
runtime (where ever it might be, or how it is named).

dependency walker:
MSVCR90.dll, CV210.dll are in the libs folder as msvcr90.dll, cv210.dll
Cxcore.dll, HighGUI.dll should be called cxcore210.dll, highgui210.dll and are in the libs folder

As far as i know: The Windows filenaming is still case insensitive, so
these differences should not matter.

But that a gpsvc.dll is reported is strange, since this is not in the
libs folder.

So is this stuff on the build machine really from an original Sikuli
package?

This should work on the build machine with original stuff from Sikuli X (preferably latest version r930):
- having a JRE 6 installed and running
- in a folder e.g. c:\SikuliX
-- sikuli-script.jar
-- a copy of the original libs folder
- in Path at runtime: c:\SikuliX\libs;path-to-java\jre6\bin
- access rights to let Java/Sikuli create a folder tmplib in the users temp folder

the on using on commandline this should work (java.exe should be found on path!):
java -jar c:\SikuliX\sikuli-script.jar path-to-your-script.sikuli

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