← Back to team overview

sikuli-driver team mailing list archive

Re: [Question #254231]: I am unable to use my own libVision.so (Linux)

 

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

    Status: Answered => Solved

David Inman confirmed that the question is solved:
1. If 1.1.0 already has Ruby support, that would be great.  JRuby support, however, does not work for me.  I use it sometimes,
but its not viable for some applications - the VM can be both slow and fast, not to mention a perpetual list of problems with gems that include C extensions.  Ideally I would like both.  Are both JRuby and Ruby supported (may in the fashion of the sikuli-server gem)?

2. I was using 1.0.1 and had some luck with libVision.so there.
However, 1.1.0-Beta4 is what I'm trying to use now because of its
feature set.  When I started modifying the sikuli-server gem to support
more commands I quickly gained appreciation for what I would need and
found 1.1.0 desirable.  I'm able to get the 1.1.0-Beta4 IDE to start,
but it does not work with libVision.so.

3. I did not know.  I wish I did.  I'll see if I can find the Ruby-
related code.

RE: helping.  I'm thrilled to help, but I'm quite frustrated with the build system, I cannot tell what I'm doing wrong versus what might be broken due to development changes.  I really don't know what commands I'm supposed to run to get a libVision.so to work.  I have read suggestions on this site and via google, but when I try the suggestions I simply get too many errors, don't
know if they are real,  and the result does not work.  I don't know enough about the maven targets (or maven) to address only what I need.  If I were to be given a little direction on how libVision is incorporated, I think I could fix what is broken either in my code or Sikuli.

Thanks,
Dave

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