0 Replies - 155 Views - Last Post: 21 June 2012 - 12:12 PM Rate Topic: -----

#1 Zel2008  Icon User is offline

  • D.I.C Addict

Reputation: 14
  • View blog
  • Posts: 790
  • Joined: 06-January 09

JNI issues

Posted 21 June 2012 - 12:12 PM

Hi all,

I have a C++ dynamic library that I linked to a Java front end using JNI. I know how to load it, and my System.loadLibrary call to do so runs just fine. Up until a few days ago, everything in the library worked fine from Java, too. I added a few new classes, though, and now I get UnsatisfiedLinkErrors whenever I try to access them through Java.

And here's the weirdest part -- The JNI has the ability to be self-contained, so when the code isn't moved from the directory it's built in, and connected to a small self-contained program, it works fine. The issue occurs only when I move the JNI code to another directory and try to link it with another piece of software.

So, this leads to the following question -- is there something inside JNI code that tells it that it can only be used from a specific directory? If so, how can I turn that off?

I'd appreciate any insight on this.

Thanks,
Zel2008

Is This A Good Question/Topic? 0
  • +

Page 1 of 1