Sikuli Script is an amazing way to script GUI based actions. The script you write is based almost entirely on screenshots (with obviousy text commands to click, doubleclick, and things like that).
The real downfall here, is that Sikuli was seemingly designed from the ground up for OS X 10.5 and 10.6 (Leopard and Snow Leopard). The Windows version works great, however if you install it on a 64-bit version of Windows, it wont even run, you get nothing. To fix this we need to go to the batch file which runs Sikuli, usually located in
C:\Program Files\Sikuli\Sikuli-IDE.bat
You will need to change it to look like this.
@echo off
PATH=%PATH%;%~d0%~p0\tmplib
“C:\Program Files (x86)\Java\jre6\bin\java.exe” -Dpython.path=”%~d0%~p0\sikuli-ide-full.jar\Lib” -cp “%~d0%~p0\sikuli-ide-full.jar” edu.mit.csail.uid.SikuliIDE %*
Save it and now just run that .bat file instead of the .exe, as the .exe file still wont work to launch the Sikuli GUI.
The only real downfall to this method is .skl files wont launch unless you set them to launch with the .bat file you just edited. After you do that, they run just fine (with a java window that pops up and closes when it’s finished the script).
![[Valid Atom 1.0]](http://feed2.w3.org/images/valid-rss-rogers.png "Validate my Atom 1.0 feed")
can you show example of the last paragraph ? thanks
[Reply]
Corey Reply:
October 14th, 2011 at 8:31 AM
@rob, I don’t have Sikuli installed right now to demo, but if you hold shift and right click the .skl file you should get an “Open With…” option. From there browse to the .bat file we made in the earlier steps.
[Reply]
Even those fixes won’t work if you are trying to integrate Skiuli with other tools, such as for example using Watir to drive the browser, and Sikuli to deal with annoying difficult to automate proprietary stuff like Flash.
I was in a situation where the IDE worked, but doing anything scripted failed with an error message relating to the win32util.dll file that comes with Sikuli (and is apparently only provided compiled for 32 bit).
I was able to get that to work, but I had to install 32 bit versions of the Java runtime stuff and most importantly 32 bit versions of Jruby. Once all that stuff was setup for 32 bit, I was able to use Sikuli in Watir scripts running under JRuby.
Normally you’d think ‘I’ve got a 64 bit box, so I’ll install the bits for 64 bit.. but that fails where the current Sikuli is concerned. Revert anything related to both Jruby and Java back to 32 bit however and you should be good to go.
[Reply]
Corey DeGrandchamp Reply:
October 24th, 2011 at 5:15 PM
@Chuck vdl, Thanks for the clarification Chuck. I should have mentioned in the post about the requirement of 32-bit java.
My explanation was for a system with 32 bit and 64 bit co-existing from what I remember (It’s been a while…)
Thanks for the jruby details though, much appreciated. as I’m sure it will help someone in the future who ends up here.
[Reply]