Question #235975 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/235975
RaiMan posted a new comment: @Brian Brown --1: it is SIKULIX_HOME ... ... with version 1.0+ to allow some coexistence with RC3. ... and it is not needed in 99% It is strongly recommended to not move around the Sikuli stuff (especially on Windows because of the libs path challenge). Keep it in one folder (e.g. c:\SikuliX). When running any of the Sikuli packages, the environment is checked, the libs are exported from the jar to a libs folder preferably in the same folder as the jar itself and on Windows the path is setup in the registry if needed. So if you keep it simple this way, you do not have to do anything, but run the setup and in doubt check, wether the system path is setup correctly. --2: jawt.dll ... to avoid this additional entry %JAVA_HOME%\jre\bin in the system path only for this one lib, jawt.dll is now (1.0+) copied to the Sikuli X libs folder at startup, so it is found without this additional entry. ( a system path entry for Java is not needed any way in the system path and is in doubt blocking the dynamic switching of Java versions - only a JAVA_HOME in the system environment might be needed for some applications) -- Conclusion - SIKULI_HOME is not recognised by SikuliX 1.0.1 anyway - SIKULIX_HOME is not needed, as long as you allow Sikuli to create and setup the libs folder in the same folder as the active jar - a system/user path entry is created by Sikuli automatically - a %JAVA_HOME%\jre\bin in the system path is not needed any longer (and not recommended) 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
