🚀 go-pugleaf

"Jason Burton" <Jason.Burton@McLeodSoftware.com> wrote:

>>Jason:
>>
>>Perhaps the dll you call has dependencies to other dlls?  That's
>>another cause that springs to mind.
>>
>>-Rich
>
>
>I would think that the DLL uses the Windows system DLL's but it doesn't use
>anything else.  I am able to access the DLL fine with other languages (i.e.
>the DLL is setup correctly on the machine I am using).  My real question was
>am I forgetting something?
>
>In the class, I do
>
>static
>{
>    System.loadLibrary("pcmgw32");
>}
>
>public native long PCMGCreateMapChild(long parentHandle);
>
>Assuming that the specified native function exists in the specified library,
>is that everything that must be done to access this function?  The library
>seems to load fine, but calling the function gives the UnsatisfiedLink.

When you call a function from Java, the DLL routine that it actually
looks for a) is decorated (mangled) with the package/class details of
the calling class, and b) has very much its own set of calling
parameters - read the JNI specification for details, although one or
two bits require educated guesswork and experimentation since the
descriptions are rather terse.

I would think that you will have to create your own set of "wrapper"
fns in a new DLL of your own, which the JNI can relate to. These
wrappers then call the 3rd-party reoutine and relay back the results.

Be careful about calling conventions in Widows, and declare any fn you
want to call via JNI as extern "C" if you're working in (or your
compiler is working in) C++.

WIll Dickson.

>
>Thanks,
>Jason
>