It's possible that there is a dependency from LeapJava.dll to Leap.dll within the native code. This is not something that OSGi can directly influence. However it does not mean all hope is lost, please read the following excellent wiki page on the subject (thanks again to Holger Hofstaette): http://wiki.osgi.org/wiki/Dependencies_In_Native_Code
Neil On Thu, Jul 25, 2013 at 1:49 PM, pigelvy <[email protected]> wrote: > Hi all, > > I'm trying to use the new Leap Motion > <https://www.leapmotion.com/developers> but I end up with an > EXCEPTION_ACCESS_VIOLATION. > > In my manifest I declare the Bundle-NativeCode such as > > <Bundle-NativeCode> > x86/Leap.dll;x86/LeapJava.dll;osname=win32;processor=x86 > </Bundle-NativeCode> > > Of course: > - I tried something with the same libraries outside OSGi and it works > - the two libraries are in my bundle in the x86 folder > - "osname=win32;processor=x86" work for other bundles > > After decompiling the Leap Motion jar, I saw that LeapJava.dll is the only > library that is loaded (using System.loadLibrary("LeapJava")). Is it > possible that then do not load their other library correctly? > > Any idea? > > > > -- > View this message in context: > http://apache-felix.18485.x6.nabble.com/Leap-Motion-in-OSGi-EXCEPTION-VIOLATION-EXCEPTION-tp5004404.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
