sikuli-driver team mailing list archive

[RaiMan <question237289@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
--- at comment #7
As already mentioned: I used MinGW to produce the libs.

libgcc_s_dw2-1.dll
libstdc++-6.dll
These are the runtime support to access the Windows API needed by MinGW built dlls.
You will have to include the respective MS VCxx runtime support.

I built everything from sources, so I made a liblept without gif support.
If you use a prebuilt liblept, you have to add what is needed.

JIntellitype.dll is from the respective Java package to support hotkeys.
WinUtil.dll is the interface to support system specific things mostly for the App feature.

Since you want to concentrate on the Vision stuff: just use them as is
(not relevant for VisionProxy)

--at comment #6:
- did you fix it?
seems that your build procedure does not yet produce a useable VisionProxy at the moment.
VisionProxyJNI.new_FindInput__SWIG_0()J  is an entry expected in VisionProxy.dll

The SWIG generated file org.sikuli.basics.proxies.VisionProxyJNI.java has all signatures for the JNI entry points expected in VisionProxy.dll
The SWIG generated native counterpart is visionJAVA_wrap.cxx

as already mentioned, you might check your dlls with a dependency
walker.

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