For the past couple of weeks, we've been working on adding support for Maven in the Jogamp projects. We've just made a test repository public at http://jogamp.org/deployment/maven with the intention of getting the Jogamp artifacts into Maven Central for 2.0-rc10 (or thereabouts).
Please see the wiki for instructions regarding setting up Maven to resolve dependencies from this test repository, and for details on how to add Jogamp as a dependency in your Maven projects. Please note that only "gluegen-rt" and "jogl-all" are currently available: We'll be adding the rest (jocl, joal, etc) soon, assuming a lack of disasters with the current deployment method.
Note that the jar files available here are marked as 2.0-rc9 but do differ ever so slightly from those published in the 2.0-rc9 release made recently. The changes were made to allow Jogamp to work with jar files that contain version numbers (as Maven requires them to be versioned), so don't panic if the checksums don't match what you'd expect to see. See the relevant bugzilla thread for the gory details.
I'll be monitoring this thread for problem reports, animal sacrifices, large monetary donations, and more!
Great, thanks a lot for this - very much appreciated.
Works fine for me on Linux, but fails on Solaris:
Exception in thread "main" java.lang.UnsatisfiedLinkError: /var/tmp/jogamp_0000/file_cache/jln7353987052733021139/jln9095812076311097144/libgluegen-rt.so: ld.so.1: java: fatal: libgcc_s.so.1: open failed: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
$ uname -a
SunOS marlin 5.11 snv_134 i86pc i386 i86pc Solaris
Just wanted to add that we've decided to link libgcc statically. It'll be in rc10, when that
appears. The difference in file size for the resulting binaries is too small for 'du' to register,
so it seems there's no good reason to avoid doing it.
Using the Sun Studio compiler should work as well (unless there's c++ code involved somewhere, which would mean you'd have to use the same compiler for everything, since c++ doesn't have a standardized ABI).
On 07/31/2012 03:48 PM, io7m [via jogamp] wrote:
> It's actually Sven that provides the compiled binaries for all platforms,
> and I think he produces the Solaris binaries on OpenIndiana. Is Sun Studio
> available there?
No, and I am sort of reluctant to re-attempt to purchase an Solaris license
and utilize the proprietary compiler, which shall not give us any benefits.
> I may be wrong, but I was under the impression that libgcc only provided
> support code for exception handling and for compiler intrinsics. Should be
> system-independent. I'd like to know if I'm wrong, though.
This is my assumption as well.
Adding the static libgcc should work here.
However, until I am back from SIGGRAPH I will refrain from
these changes which may have a huge impact.
Note: We planned to add the static libgcc for all platforms
since the costs (memory footprint) is close to zero, regarding Mark's analysis.