sikuli-driver team mailing list archive

[RaiMan <question231849@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
Currently moving sikuli-script.jar around or packing it together with
other jars is a problem.

If nothing else is said, Sikuli expects the libs folder to be in the
same folder as sikuli-script.jar (or the jar containing it).

On the other hand it is generally not recommended to move sikuli-script.jar around or pack it into fat jars.
You should leave it in one place outside your project environment and use references in IDE's (not physical copies) and -cp at runtime outside of IDE's. In this case, libs folder will always be found.

If you want to use other approaches, that lead to the above error, then
you currently  have these options:

- set environment variable SIKULIX_HOME to point to the folder containing the libs folder
- use -Dsikuli.Home as JVM commandline option the same way

I have currently revised the libs concept: the native libs are contained
in sikuli-script.jar and are deployed to the outside world at runtime
with different options (will be available with the service update end of
July and earlier as Beta)

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