Support of windows-amd64 system is broken!

The following libraries, though referenced in the various jnlp files are not found on the site:

gluegen-rt-natives-windows-amd64.jar
jogl-natives-windows-amd64.jar
nativewindow-natives-windows-amd64.jar

Hence support for Windows am64 systems is broken.

They libraries were working fine when JOGL was maintained at java.net.

http://jogamp.org/deployment/autobuilds/jogl-b167-2010-09-14_16-31-14/build/

On 09/16/2010 11:34 AM, Rana [via jogamp] wrote:

The following libraries, though referenced in the various jnlp files are not found on the site:

gluegen-rt-natives-windows-amd64.jar
jogl-natives-windows-amd64.jar
nativewindow-natives-windows-amd64.jar

Hence support for Windows am64 systems is broken.

They libraries were working fine when JOGL was maintained at java.net.

---

View message @ http://jogamp.762907.n3.nabble.com/Support-of-windows-amd64-system-is-broken-tp1486942p1486942.html
To start a new topic under jogamp, email [hidden email]
To unsubscribe from jogamp, click here.

-- 
http://michael-bien.com/

Hi Michael,

While using the JOGL 2.0 libraries, I realized that due to the sweeping changes in the APIs and packages, my current codebase will not compile until I spend substantial effort in migration.

1) Is there any decent guide on how to migrate applications from jogl 1.1.x to 2.0?

2) Can you point me to the last 1.1.x release so that I can support windows amd64 systems without migrating right away?

Thanks and regards,

Rana

If your source code is very big, maybe use Jackpot 3.0. Otherwise, doing it by yourself is not very difficult. The main differences are below:

// get the profile
GLProfile profile = GLProfile.getDefault();
// this allows us to set particular properties for the GLCanvas
GLCapabilities glCapabilities = new GLCapabilities(profile);
instead of
GLCapabilities glCapabilities = new GLCapabilities();

final GL2 gl = GLContext.getCurrentGL().getGL2();
instead of
final GL gl = GLContext.getCurrentGL();

Except that, the package names have changed, some packages have moved from com.sun to com.jogamp, it is quite trivial. Instead of using directly GL, lots of thing are in GL2, GL2GL3 or in another interfaces of this kind. Sorry for my approximative explanation.

Julien is right, there are only minor differences between both APIs.

you could take a quick look at the tutorials e.g:
https://sites.google.com/site/justinscsstuff/jogl-tutorials

to get an explanation how the new initialization works.

I also wrote a blog entry about profiles some time ago:
http://michael-bien.com/mbien/entry/jogl_2_opengl_profiles_explained

for further questions just ask (we also have a jabber chatroom)

regards,
michael

On 09/22/2010 11:46 AM, gouessej [via jogamp] wrote:

If your source code is very big, maybe use Jackpot 3.0. Otherwise, doing it by yourself is not very difficult. The main differences are below:

// get the profile
GLProfile profile = GLProfile.getDefault();
// this allows us to set particular properties for the GLCanvas
GLCapabilities glCapabilities = new GLCapabilities(profile);
instead of
GLCapabilities glCapabilities = new GLCapabilities();

final GL2 gl = GLContext.getCurrentGL().getGL2();
instead of
final GL gl = GLContext.getCurrentGL();

Except that, the package names have changed, some packages have moved from com.sun to com.jogamp, it is quite trivial. Instead of using directly GL, lots of thing are in GL2, GL2GL3 or in another interfaces of this kind. Sorry for my approximative explanation.

http://tuer.sourceforge.net
http://gouessej.wordpress.com

---

View message @ http://jogamp.762907.n3.nabble.com/Support-of-windows-amd64-system-is-broken-tp1486942p1560071.html
To start a new topic under jogamp, email [hidden email]
To unsubscribe from jogamp, click here.

-- 
- - - -
http://michael-bien.com