Databases
StackOverflow2013
Postsdbo
POSikuli UnsatisfiedLinkError when using sikuli-script.jar
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSikuli UnsatisfiedLinkError when using sikuli-script.jar
    text
    copied!<p>I'm on Windows 7 32bit, Java JRE6 31 installed and using Sikuli X 1.0rc3. I want to launch a test with sikuli-script.jar like this:</p> <pre><code>java -jar c:\sikuli\sikuli-script.jar test.sikuli </code></pre> <p>All I get is this error message:</p> <pre><code>java.lang.UnsatisfiedLinkError: java.lang.UnsatisfiedLinkError:C:\sikuli\libs\VisionProxy.dll: Can't find dependent libraries </code></pre> <p>I have set all the environment variables needed, so my PATH looks like this:</p> <pre><code>PATH=...;C:\sikuli\libs;C:\Program Files\Java\jre6\bin SIKULI_HOME=C:\sikuli </code></pre> <p>I can use the IDE and launch the tests there etc. But only if I use the <code>Sikuli-IDE.exe</code> the <code>sikuli-ide.bat</code> and <code>sikuli-ide.jar</code> don't work either. Always with the same error from above. So I think in the build process of the .exe file they added some magic, but I can't figure out what it is. </p> <p>Does somebody have a similar problem? Or even a solution?</p> <hr> <h2>Update</h2> <p>As I wrote below, it works out of the box with my new computer. :D But maybe my solution can help someone. </p> <p>Sikuli Team uses <a href="http://launch4j.sourceforge.net/" rel="nofollow">Launch4J</a> to build the <code>Sikuli-IDE.exe</code> out of the <code>sikuli-ide.jar</code>. They use <a href="https://github.com/sikuli/sikuli/blob/develop/sikuli-ide/l4j-conf.xml" rel="nofollow">this</a> config file. I modified it slightly and created a <code>Sikuli-script.exe</code>. It was pretty simple but I lost the config file unfortunately. </p> <p>Hope I could help!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload