sikuli-driver team mailing list archive

[Jordan Beland <question175086@xxxxxxxxxxxxxxxxxxxxx>]

New question #175086 on Sikuli:
https://answers.launchpad.net/sikuli/+question/175086

I am currently working on using Sikuli as part of our project built with java using eclipse, and we run on an OSGI framework on many machines. As such, it isn't practical to be adding the .dll library directories to our path. I noticed in the source code that some of the .dll's were extracted to a new folder, and then loaded from there. Is there a specific reason for using this over system.loadLibrary()? Our goal would be not to have to modify the path, but to be able to reference a directory contained in our project that has all of the required libraries (and dependent libraries) to load.  

I ran a few tests with calling system.loadLibrary on the .dll's within our own code which was called before sikuli was loaded, and that loaded them fine, but then it crashed on the nativeLoader call.

Is there any known work arounds for this (other than modifying the path variable)?

Thanks,
Jordan

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