sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #13210
Re: [Question #208801]: Yet another java.lang.UnsatisfiedLinkError
Question #208801 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/208801
Status: Open => Answered
RaiMan proposed the following answer:
I tested on my Win 7 (should be no difference on Win XP with these
basics) and it works as expected.
for interactive Sikuli session (should be same for a script)
(I had this in a runsik.cmd and ran it from the stick directory)
The original path only contains the jre6/bin-reference.
set SIKULI_HOME=I:\QA\sikuli\Sikuli-X-1.0rc3\Sikuli-IDE\
set PATH=%PATH%;%SIKULI_HOME%libs
@echo ****PATH: %PATH%
java -cp "%SIKULI_HOME%sikuli-script.jar" -i
A problem is, that this path manipulation always adds to the path again, if it is run again in the same command session.
So if you change your batch script and rerun it, the old path is used, which might be the cause for your c: problem.
So for every rerun, you must restart the commandline also, if you do not
assure that always the base path is used.
One more problem I had: since I have both Java 6 and Java 7 on my
machine, I had to assure, that the java command from JRE6 was used. The
only fix I found for that was to use the explicit java.exe location
(whatever else I did, java always used Java 7):
"C:\Program Files\Java\jre6\bin\java.exe" -cp "%SIKULI_HOME%sikuli-
script.jar" -i
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.