sikuli-driver team mailing list archive

[RaiMan <question241257@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
--- Maven Central
... SikuliX is not yet there. I will have it there after I am ready with version 1.1.0 early in 2014.

until then you either have to install it into your local repo or use a
dependency declaration like yours.

BTW: since you are using Maven, I suppose you develop in plain Java. if
this is true, then you do not need sikuli-script.jar. This is simply
sikuli-java.jar + Jython script run support with a bundled Jython
package. So if you only use Java or even Jython scripting with your own
Jython installation (or IDE support) sikuli-java.jar is the only thing
you need.

--- Sikuli Java apps on other machines
... if you only want to run your app on another machine with the same system (Windows in your case), you do not need any "installation".
The only thing needed is the sikuli-java.jar, that you already used.
You even might make a fat jar (Maven assembly plugin), that completely contains sikuli-java.jar.

The most ugly thing with Sikuli on Windows is the fact, that you need a
ref to Sikuli's libs folder in the system path at runtime.

If it is possible, to use a command file, to start your app, then the
easiest solution is to wrap the java execution into setlocal/endlocal
with a PATH=<path-to-sikuli-libs>;%PATH% before the java execution, so
the needed path entry is temporary for the current run (this is how the
Sikuli command files do it: sikuliIDE.cmd and sikuliScript.cmd).

At runtime Sikuli first checks the existence of the libs folder. If none
exists or the existing one is invalid, the libs folder usually is
created in the folder, where the jar is and filled with the libs by
export from the jar.

On Windows additionally it is checked, wether a ref to this libs folder
is in the system path. If it is not, then Sikuli adds it via registry.
But you have to restart the app or even your session (logout/ login).

BTW: on Windows, the same sikuli-java.jar works with Java 32-Bit and
Java 64-Bit: at runtime simply the library set is changed dynamically
via export from jar.

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