Hi,
I’m new in OpenAL. I have installed the OpenAL SDK 1.1. The Demos are working properly,
but I do not know how to set the paths for OpenAL and Joal, that JBuilder can find them.
What do I have to do to make it working.
Thanks
der Diggi
Hi,
I’m pretty serious about that.
Does anyone know where I can find instructions to set up joal and openal.
Actually everyone of you know how to do that. Why can’t you give me an answer. I would really apriciate it.
Diggi
I don’t think anybody has experience with JBuilder specifically. You need to get joal.jar on your application classpath and the joal_native.dll / libjoal_native.so on to the path specified via -Djava.library.path.
Ok,
sure I can not expect everyone to work with JBuilder. But it would be good to know that stuff in generel. Are there any instructions for other Java Editors?
I don’t know about other editors but the post above shows you what you have to configure. You need to get the jar file onto your CLASSPATH and the DLL/.so file onto your java.library.path. You might want to try to get the demos working on the command line first to get a better understanding for what you need to set up in the IDE.
Ok, thanks first,
I’m using windows xp. I got the following files:
joal.jar
joal_native.dll
SingleStaticSource.class
(All these files came from the lesson1 tutorial).
What do I have to write in the command line to execute the .class file properly?
Do I need additional files to run the file?
I installed the openal sdk 1.1. Do I have to do some settings for that? Lesson1 was supposed to run with 1.0. Is it working on 1.1 as well?
Thank you very much for taking the time
Diggi
ps: I was trying a couple of things, but I couldn’t make it work
In the current joal-demos.jar SingleStaticSource is in a sub-package so it’s easier to start with that jar than the class file.
java -classpath joal.jar;joal-demos.jar -Djava.library.path=. demos.devmaster.lesson1.SingleStaticSource
You need to look at javac’s documentation and get a good feel for the -sourcepath, -classpath and -d options when compiling new code.
Everything is working fine with the OpenAL 1.1 SDK from http://openal.org/ . All of the new entry points are exposed in the current JOAL build.
I tiped in what you told me to. When I hit the return button, it seems as it was doing nothing. But when I changed the name of the jar and the dll. It supported an exception in main thread. So it musst have been executed, but I couldn’t see anything on the screen rather hear anything.
I think there musst be any generel openal settings, that need to be set. I only installed the openal sdk 1.1 and did nothing else with it. What do I have to do to make it work??
Thanks a lot for the help
OK, ok, never mind. I reinstalled the sdk and no it is working.
So I think we can close this thread now.
Thanks again
I have the start of my JOAL documentation at: http://www.starfireresearch.com/services/java/docs/joal.html (simple basics on getting up and running)
Are you sure you’re running the most recent JOAL release? The error messages and diagnostic printlns in your documentation look like you’re using the pre-January 2006 version. The nightly builds on the JOAL home page should also work.
Ken, the top section is for the new JOAL, that detailed section was written by a friend and is for the pre-January 2006 release. I’ll modify the page to make that more clear.
The top section indicates there is a println “in alutInit(): Device Name = null”. There is no such println in the current JOAL.
Thanks Ken, I just tested and that does not apply any more. I’ll try and fix up my webpage this evening.