sikuli-driver team mailing list archive

[RaiMan <question205842@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
This is from evaluations on Windows 7 32-Bit.

If you do not install Sikuli in its (currently) standard place (
c:\Program Files\Sikuli X ), then things get a bit tricky:

- Sikuli first looks for the primary DLL's (VisionProxy, Win32 and VdictProxy) in c:\Program Files\Sikuli X\libs (which is hard coded :-(
- If there, these DLL's are loaded from there
- if not there (which is the case if you never installed Sikuli in its standard way), then it copies these 3 DLL's from inside sikuli-script.jar to the users temp directory into the folder tmplib (Java standard environment property), usually
c:\Users\user-name\AppData\Local\Temp\tmpdir
from where the Java native loader loads these primary DLL's (since native code cannot be loaded from the jar directly)
- all the secondary DLL's are then found on the PATH at runtime, no matter how this was setup before and where the original contents of the Sikuli\libs folder might be. 

Conclusion: Sikuli does not look for the 3 primary DLL's on the PATH ,
but hardcoded at c:\Program Files\Sikuli X\libs and if it is not there,
it copies the DLL's to a temp folder to load it from there, no matter
what the PATH might tell.

So usually in these cases (there is no c:\Program Files\Sikuli X\libs),
the problem might be, that for some reason the creation of the above
mentioned tmplib folder is not possible (e.g. access right problems).

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