Some gluegen BufferFactory methods not found

I'm setting up JOGL JSR-231-2.0 beta10 on Win 7 with Eclipse and jdk 1.6 u20.  I have been able to run some of the JOGL examples (eg, Gears) using the JNLP versions on the web.  However, when I downloaded the libraries and the example source and tried to run Gears directly in Eclipse, I get method not found errors.  I've scrubbed the disk of all versions of gluegen-rt etc except the one in the beta10 directory.  I wrote a little java source that attempts to call various methods from BufferFactory.  All the methods are visible in the Eclipse package explorer, but some (isLittleEndian(), nativeOrder(ByteBuffer)) cause compiler errors as being not defined.  (See attached screenshot.)

I can't figure out why this is.  Does anyone have any suggestions?

Thanks.

Doug

On Tuesday, June 01, 2010 03:46:14 Douglas W Johnson [via jogamp] wrote:
>
> I'm setting up JOGL JSR-231-2.0 beta10 on Win 7 with Eclipse and jdk 1.6 u20.
Hi Doug,

I am not familiar with the version you mention
        'JOGL JSR-231-2.0 beta10'
or should I ? Have I deployed it while at Sun ?

However, all those versions are very much outdated and I even reject
looking at this code right now, until this is tested and reproduced
with our current versions at jogamp.org.
I hope you understand.

> I have been able to run some of the JOGL examples (eg, Gears) using the JNLP
> versions on the web.  However, when I downloaded the libraries and the
> example source and tried to run Gears directly in Eclipse, I get method not
> found errors.  I've scrubbed the disk of all versions of gluegen-rt etc
> except the one in the beta10 directory.  I wrote a little java source that
> attempts to call various methods from BufferFactory.  All the methods are
> visible in the Eclipse package explorer, but some (isLittleEndian(),
> nativeOrder(ByteBuffer)) cause compiler errors as being not defined.  (See
> attached screenshot.)

A screenshot for compiler feedback ?
This overkill is even new to me :)

For sure you are mixing something here, but read above.

>
> I can't figure out why this is.  Does anyone have any suggestions?
>

http://jogamp.org/jogl/doc/HowToBuild.html

> Thanks.
>
> Doug
>
> http://jogamp.762907.n3.nabble.com/file/n860118/gluegen-method-not-found.png 
>

--
health & wealth
mailto:[hidden email] ; www  : http://www.jausoft.com ; pgp: http://www.jausoft.com/gpg/
land : +49 (471) 4707742 ; cell: +49 (151) 28145941
Timezone CET: PST+9, EST+6, UTC+1

Sven:

Thanks for your reply.  I believe what you are saying is "build from sources".  Okay, will do.

But to show you how I got to this point ...

The JOGL Userguide page on jogamp.org has this:
--
Most developers using JOGL will download the most current release build. Separate instructions are available on how to build the source tree.

If you are developing a new application which uses JOGL, download the zip archive for your platform (for example., jogl-[version]-windows-i586.zip) and unzip it. Modify your CLASSPATH environment variable to include the full paths to jogl.all.jar, nativewindow.all.jar, gluegen-rt.jar, and optionally newt.all.jar.
--
If you follow the "release build" link, you get to an Index of /media/jogl/builds/archive/.  As far as I could tell, 2.0 beta 10 was the most current release.  Apparently, I was wrong.

As for the screenshot, I wasn't trying to provide compiler feedback, I was trying to provide context for a question about your libraries.  Since I found the symptom hard to believe, I thought it was better to show that than have a long chain of replies trying to explain it.  Of course, since I'm apparently using old libraries, it is not nearly so interesting.

Onward and upward.

Doug

On Tuesday, June 01, 2010 17:14:28 Douglas W Johnson [via jogamp] wrote:
Sorry .. that userguid is old.

However, you may try out our 'nightlies', ie autobuild ones:

http://jogamp.org/deployment/archive/
http://jogamp.org/deployment/autobuilds/

This is clearly visible on the jogamp.org frontpage,
look for 'Builds' !

Sorry for the inconvenience, and thx for the info about our userguide,
so we have to fix that, sure.

We will hopefully be ready until Siggraph 2010,
all shall be working until then.

~Sven

Sven:

I took all the Java installations off my system and went back to bare metal as far as Sun was concerned.  I reinstalled JDK 6u20 and linked to the files from jogl-2.0-pre-20100512-windows-i586.zip.  Gears example now runs in Eclipse with no problem.

In addition to my using an outdated JOGL library earlier, I think there were little bits of older installations of various 3D libraries still floating around that were tangling up with JOGL even though I had tried to scrub for that.

Thanks.

Doug