Login  Register

Re: Maven / Hudson integration

Posted by Wade Walker on Mar 18, 2011; 1:27am
URL: https://forum.jogamp.org/Maven-Hudson-integration-tp2671009p2696220.html

Thomas Welsch wrote
A better and simpler way (from my side of view) would be using different names for the JNI libs for each architecture. Then we can always install all JNI libs and using one library path (so I don't need the "build.type" selection in the maven scripts and the "classifier" in the maven artifacts.)
Hi Thomas,

A system like you mention (all native libraries named uniquely for platform and architecture) seems like it could work, though I haven't seen it done. If it's any consolation, I have this same situation in my Eclipse RCP apps -- I have to download all the native libraries and put them in separate directories to let them coexist

The current system does simplify the Java library loading code a lot. First, you can always just say loadLibrary( "gluegen-rt" ) instead of loadLibrary( "gluegen-rt" + platform + arch + version ). And it also saves you having to write code to simplify the os.name, os.arch, and os.version information down into the subset of names that actually require different libraries (so you don't have copies of the same library that differ only by name). For example, "gluegen-rt-64-Windows7.dll" is the same library as "gluegen-rt-64-WindowsVista.dll", so you'd really just want one DLL, and Java code to map those names together.