joal problem1

Hello! I got an exception at initial state:

[code]
        try  {
            ALut.alutInit(); //here
            al = ALFactory.getAL();
            al.alGetError();
        } catch(ALException alexception) {
            alexception.printStackTrace();
            return false;
        }
[/code]

here is the stack trace:
[code]
Exception in thread "main" java.lang.NoClassDefFoundError: com/jogamp/common/os/DynamicLibraryBundleInfo
        at com.jogamp.openal.ALFactory.initialize(ALFactory.java:58)
        at com.jogamp.openal.ALFactory.getALC(ALFactory.java:92)
        at com.jogamp.openal.util.ALut.alutInit(ALut.java:66)
        at SingleStaticSource.initialize(SingleStaticSource.java:164)
        at SingleStaticSource.<init>(SingleStaticSource.java:114)
        at SingleStaticSource.<init>(SingleStaticSource.java:23)
        at SingleStaticSource.main(SingleStaticSource.java:242)
Caused by: java.lang.ClassNotFoundException: com.jogamp.common.os.DynamicLibraryBundleInfo
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        ... 7 more

[/code]
I've been imported to my build path latest build of joal.jar (feb 9)...
any suggestions? thanx.

On Wednesday, February 09, 2011 11:57:45 dim_9999 [via jogamp] wrote:
you need gluegen-rt.jar

> I've been imported to my build path latest build of joal.jar (feb 9)...
> any suggestions? thanx.

~Sven

Thanks.  i used jogl-1.1 with joal-2...

  just use JOGL 2 and it should be all fine.

-michael

On 02/09/2011 05:39 PM, dim_9999 [via jogamp] wrote:
> Thanks.  i used jogl-1.1 with joal-2...
>
> _______________________________________________
> If you reply to this email, your message will be added to the discussion below:
> http://jogamp.762907.n3.nabble.com/joal-problem1-tp2457665p2459642.html
> To start a new topic under jogamp, email [hidden email]
> To unsubscribe from jogamp, visit
http://michael-bien.com/

At first, glDeleteBuffers frees the OpenGL identifier or marks it as available and triggers the destruction of the data store on the GPU. It doesn't destroy the storage on the CPU (for example if you create your own direct NIO buffer).

Use the cleaner to release the native resources of a direct NIO buffer you created (until Java 1.9 provide a public API to do that).