sikuli-driver team mailing list archive

[tombrus <question251774@xxxxxxxxxxxxxxxxxxxxx>]

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

I am running sikuli in a jenkins job on ubuntu to test our own product.
When I installed opencv it gave me the 2.4 version (libopencv_core.so.2.4).
I rebuild the libVisionProxy.so, all seems to work fine.

I recently added a jenkins job for building sikuli itself from git, just for fun.
July 14 it gave me a green build, July 16 around 11:00 it gave me a red build.
Not really a big problem, it was for fun anyhow... but the tests of our own product started to fail as well at that time... why?

I sorted it out and the following was happening:
    - the sikuli job was failing because it needs the 2.3 version of opencv (libopencv_core.so.2.3). 
      As a side effect of the build it left a SikuliX/libs folder in jenkins home dir with a libVisionProxy.so file that is dependent on libopencv_core.so.2.3 (which I do not have).
    - our own builds were failing because they erroneously use the libraries in ~jenkins/SikuliX/libs which depend on libopencv_core.so.2.3 which is not on my system.

I have three questions:
 - is there a fixed dependency on the 2.3 version of libopencv_core.so in the files in git? can that be fixed?
 - why are the cached libs stored in a home folder and not next to the jar files? This creates an unwanted interdependency.
 - can the dependency to opencv not be universal so that it accepts 2.3 as well as 2.4 (mind you, I do not know opencv!)

Just wanted to share this, no big deal, I disabled the sikuli job and removed the SikuliX folder from ~jenkins, so our own projects are green again.

-Tom

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