Re: The automatic extraction and loading of native libraries from JARs do not work in applications based on Eclipse RCP and multiple fragments
Posted by Sven Gothel on
URL: https://forum.jogamp.org/The-automatic-extraction-and-loading-of-native-libraries-from-JARs-do-not-work-in-applications-baseds-tp4025492p4025509.html
On 07/11/2012 12:36 PM, gouessej [via jogamp] wrote:
> My problem is not the same.
>
> We currently put JOGL & GlueGen class JARs into a fragment called "JoglLib",
> we put native libraries into disctinct fragments called "JoglLib.linux32",
> "JoglLib.linux64", "JoglLib.win32" and "JoglLib.win64". It works fine.
>
> When I try to use only JARs (those containing class files and those containing
> native libraries) and to put them all into "JoglLib", I get an
> UnsatisfiedLinkError. In my humble opinion, it is caused by Eclipse RCP itself
> which is not designed to use native libraries this way.Me using Eclipse Juno 4.2.0.
My setup here using the one jogamp-lib approach w/o a native library path,
hence utilizing the native Jar lib loading. No need to distinct the platform.
I was able to debugged a unit test here a few days ago.
Maven was working as well, using the m2e plugin, w/o any setup.
I was testing the maven/jogl demo as linked in our Wiki by Mark.
Dunno what 'fragment' is .. I assume some OSGi bundle thingy?
If so - indeed .. this probably needs more love.
Sorry for my lack of comprehension.
~Sven
URL: https://forum.jogamp.org/The-automatic-extraction-and-loading-of-native-libraries-from-JARs-do-not-work-in-applications-baseds-tp4025492p4025509.html
On 07/11/2012 12:36 PM, gouessej [via jogamp] wrote:
> My problem is not the same.
>
> We currently put JOGL & GlueGen class JARs into a fragment called "JoglLib",
> we put native libraries into disctinct fragments called "JoglLib.linux32",
> "JoglLib.linux64", "JoglLib.win32" and "JoglLib.win64". It works fine.
>
> When I try to use only JARs (those containing class files and those containing
> native libraries) and to put them all into "JoglLib", I get an
> UnsatisfiedLinkError. In my humble opinion, it is caused by Eclipse RCP itself
> which is not designed to use native libraries this way.
My setup here using the one jogamp-lib approach w/o a native library path,
hence utilizing the native Jar lib loading. No need to distinct the platform.
I was able to debugged a unit test here a few days ago.
Maven was working as well, using the m2e plugin, w/o any setup.
I was testing the maven/jogl demo as linked in our Wiki by Mark.
Dunno what 'fragment' is .. I assume some OSGi bundle thingy?
If so - indeed .. this probably needs more love.
Sorry for my lack of comprehension.
~Sven
signature.asc (910 bytes) | Free forum by Nabble | Edit this page |