← Back to team overview

sikuli-driver team mailing list archive

Re: [Question #230999]: Migration from sikuli rc3(r905) to Sikuli 1.0.0

 

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

    Status: Open => Answered

RaiMan proposed the following answer:
*** LOL: Apologies if it seems to be foolish ...

Sorry, but I have to apologize for the inconveniences the pure Java or Jython users had with the version 1.0.0.
I simply did not test enough for people like you with these environments.

*** what you need
- you only need the IDE package, if you want to use the Sikuli IDE in addition to Eclipse (in this case, you do not need the API package). otherwise the API package is sufficient.
- you only need Sikuli-1.0.0-SupplementalStuff with the IDE package, since it only fixes the sikuli-ide.jar
- when using the observer feature, you need Sikuli-1.0.0-SupplementalObserveOnlyOnce (fixes sikuli-script.jar)

** where to store the stuff
- so just have the selected package available unzipped somewhere outside the Program folder (I do not recommend to (or better: you should not) put the stuff in the program folder, since it is not an application and would have other drawbacks)
Use a pathname, that does not have any embedded blanks.

*** how to use sikuli-script.jar with Jython
Though I do not recommend, to copy sikuli stuff around (always use references), you might simply replace the old sikuli-script.jar with the new one in your site-packages folder in your case.
It is fully compatible and has some nice enhancements (wiki release note) 

*** take care for the native stuff (libs folder)
The other even more important topic is the libs folder: 
- you need an entry pointing to the libs folder in the 1.0.0 folder like with RC3 and this should be before the RC3 libs pointer (if you want to retain it): 
e.g. PATH=c:\SikuliX\libs;....

- Sikuli now finds the library folder automatically, if it is in the same directory as sikuli-script.jar (this is why I recommend, to keep the sikuli stuff in one place)
- ... but currently this does not work for users like you using plain Jython with caching switched on (I guess it has ;-) (sikuli-script.jar is loaded from cachedir as long as the original does not change) and there is a Java bug, that does not return a valid jar location in this case.
workaround: in system environment set SIKULIX_HOME to the folder containing the 1.0.0 libs folder. 
e.g. SIKULIX_HOME=c:\SikuliX

*** hope it helps
I am on the way with the service update 1.0.1 for July. All these problems will be fixed then.

Come back for more support.

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