Menu

java3d 1.5.1

2007-10-26
2013-04-26
  • Aleksandar Ristovski

    Hello,

    I am delaying posting 1.5.1 plugin due the issue with native library path. Currently the only solution to have java3d NativePipeline load the native library is to place native library in the fragment's root directory. This is a problem for, say, solaris-x86 target since there are two variants of the native library: one for amd64 and one for i386. I would have to create two fragments for this target, one for amd64 and one for i386 (everything else would be the same). I don't like this since I have to move libraries around and duplicate feature. It would be much nicer if we could somehow find correct library at runtime.

    The problem is described here: https://java3d.dev.java.net/issues/show_bug.cgi?id=536

    If you agree that this is an issue and should be improved, please vote for issue 536.

     
    • Aleksandar Ristovski

      Well, never mind.

      I have decided to go with repackaging. Native libraries need to be packaged in
      <fragmentroot>/os/<osgi.os>/<osgi.arch>/
      or
      <fragmentroot>/os/<osgi.os>/

      I could not, however, test on all supported platforms and feedback would be greatly appreciated.

      Thank you!

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.