sikuli-driver team mailing list archive

[RaiMan <question234253@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
Uuups, no idea.

Just tested with the same path setup in a Win 7 32-Bit using runIDE.cmd
(which is the same apart from using another jar), but had no problems.

This usually happens if there are some paths used in a script containing
blanks and are not quoted.

A candidate always is c:\Program Files

I did not have any problems with the command file until now, but you
might try to purge the stuff about the evaluating of the Java exe path
and make your own command file with fixed paths

@echo off
SETLOCAL

set SIKULIX_HOME=%~dp0
set PARMS=-Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine
 
set SIKULI_COMMAND=%*
PATH=%SIKULIX_HOME%libs;%PATH%
java %PARMS% -jar "%SIKULIX_HOME%sikuli-script.jar" %SIKULI_COMMAND%

ENDLOCAL

This has to be in the folder c:\SikuliX and on command line you have to
be in c:\SikuliX or or has to be run using c:\SikuliX\myRunScript.cmd

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