A pre-question to this would be: Is this(jogl) the Java/openGL stuff as announced by SGI and Sun at SIGGRAPH or is that still on the horizon? I’m unclear as there’s no stuff on either site apart from the press release.
So the actual question is: Is anyone working on SGI/Irix support for jogl?
There is no active port of JOGL for Irix (irritating Unix). However I would expect that you could port the X11 stuff that works on Solaris in a weekend.
OK I’m looking at doing this port myself. First hurdle is a complaint in gluegen about doing a StructLayout port. Anyone know where this is documented as there’s no comments in the code.
Ta,
Simon
OK I’ve finally got the jogl and jogl-demos stuff to build on Irix. Now I’ve got my first run-time error - any source developer’s got any ideas?
Running demos.gears.Gears we get:
CANVAS GL IS: net.java.games.jogl.impl.x11.X11GLImpl
CANVAS GLU IS: net.java.games.jogl.impl.GLUImpl
net.java.games.jogl.GLException: Error making context current
at net.java.games.jogl.impl.x11.X11GLContext.makeCurrent(X11GLContext.ja
va:141)
at net.java.games.jogl.impl.x11.X11OnscreenGLContext.makeCurrent(X11Onsc
reenGLContext.java:111)
at net.java.games.jogl.impl.GLContext.invokeGL(GLContext.java:162)
at net.java.games.jogl.GLCanvas.displayImpl(GLCanvas.java:182)
at net.java.games.jogl.GLCanvas.display(GLCanvas.java:82)
at net.java.games.jogl.Animator$1.run(Animator.java:104)
at java.lang.Thread.run(Thread.java:536)
This appears to be reporting an error in GLX.glXMakeCurrent which I think resolves to some C code somewhere. Any ideas gratefully received.
Simon
What version of the JDK are you using. I had similar errors under Linux with an NVidia video card using JDK 1.4.1_04, when I switched to 1.4.2, these issues went away. (Who does the Irix java ports anyways)
Hmmm… well 1.4.1 is the latest Irix Java version. Not sure why that would cause native code to fail - unless it’s not handling the boolean return value correctly.
Another dead end (but maybe it would explain why Java3D isn’t working quite right).
My guess is that there were several bug fixes in the AWT native interface stuff in version 1.4.2. Even though the AWT native interface stuff has been in Java since 1.3 it still seems like it is relatively new, i.e. has a few bugs. Or perhaps it is an incompatibility between the shared libraries on your system and the shared libraries that the JDK was built with. I know that I had issues with a program that did very intensive Java2D, it would crash the JVM. When I upgraded from Redhat 7 to Redhat 8 (or it might of been 8 to 9), then the problem went away–more than likely a native library upgrade fixed the problem.
The section of code that it is dying on is the native glXMakeCurrent is returning false. More than likely one of those parameters is incorrect. The first thing I would check is the FIXME regarding 64-bit systems. If that is not the issue, then I would look into where the values for those parameters are coming from and ensuring that they are retrieved in the proper way. I had the exact same (or similar) error on a multiheaded linux system when I was trying to show JOGL on a screen other than the primary. It turned out that JOGL defaulted to screen 0 which was causing the an incorrect value in the call to glXMakeCurrent. The solution to this problem was to get the default graphics device from the graphics environment and figure out what screen that was. (If you had an application that needed to be multiheaded, you could set the graphics configuration in the GLCapailities to select which screen the window should go on.) I’ve submitted my fix to Sun, but we haven’t heard anything back yet. Your problem may be related to this.
[quote]A pre-question to this would be: Is this(jogl) the Java/openGL stuff as announced by SGI and Sun at SIGGRAPH or is that still on the horizon? I’m unclear as there’s no stuff on either site apart from the press release.
[/quote]
What is the answer to this question? 
[quote]What is the answer to this question?
[/quote]
I believe that’s a “no”. The Sun/SGI stuff is still very much an unknown quantity.
[quote]A pre-question to this would be: Is this(jogl) the Java/openGL stuff as announced by SGI and Sun at SIGGRAPH or is that still on the horizon? I’m unclear as there’s no stuff on either site apart from the press release.
[/quote]
The announcement refers to the work that will be going on with JSR 231 (Java Bindings to OpenGL). This JSR is currently being reviewed and voted upon by the EC members. If the EC approves the JSR (and I don’t see why they wouldn’t) then work will begin on developing the API. We will be using the JOGL api as a starting point.
d
[quote]We will be using the JOGL api as a starting point.
[/quote]
Why not use JOGL as a starting point, middle point and ending point?
What is specific to the JSR that requires a complete and seperate API from JOGL?
Maybe nothing - but the JCP process is there to ensure nothing is overlooked.
If you look at other threads in this group you will see that some people are interested in some changes to the jogl api. Before making JOGL an official Java API we want to make sure all issues have at least been looked at and understood.
d