Question #261633 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261633
RaiMan posted a new comment: the only thing possible, is that with these manual copy actions and system path settings somehow the 32-Bit version and 64-Bit version got mixed up (due to the used concept, both versions have the same name with sikuli, but are hosted in different folders inside the jar) With SikuliX 1.1.0+ it is always the best start when having problems with the dlls, to just delete the libs folder, since it is recreated at the next run automatically according to the bitness of the used Java version. On Windows and Mac it generally does not make sense, to fiddle around with the libs, since they come prebuilt and ready to use. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
