🚀 go-pugleaf

I guess you might need to do that.... I'm using Visual C++ to
interface to a custom API dll so I'm writing a wrapper dll to just
what you're thinking... I'm hoping I'm also doing the right thing...
when building this dll, I link into the real dll by including the lib
file of the dll.

The an example func of the original api looks like:
DLLExport BOOL setDebugMode(BOOL bDebug);

for JNI interface, I'm doing....

extern "C"
{
JNIEXPORT jboolean Java_JNI_P4API_setDebugMode (JNIEnv *env, jobject
obj,    jboolean bDebug )
{

	jboolean res = setDebugMode(bDebug);
	return res;

}


where JNI is my package name, P4API is my class name.

sergio...

P.S. if  you find a good reference on the net let me know... I'm using
stuff from Sun's Site, but would appreciate other examples...


On Sun, 3 Jan 1999 09:46:43 -0500, "Suneet Shah" <suneet@diamelle.com>
wrote:

>Hello:
>
> I am trying to use jni to call functions in an NT dll from a product that I
>need to interface to.  The docs. that I have read indicate that for the
>integration to occur, java uses a mapping scheme such as the following:;
>
>packageName_className_functionName()
>
>this approach does not lend itself well to using a dll that comes with an
>existing library - which obviously will not follow that naming convention.
>
>How do I interface with this dll?  Do I need to write a wrapper dll that
>will follow that format?
>
>Thanks
>Suneet
>
>