RE: [Flightgear-devel] Latest OpenAL for new build?
Norman Vine wrote: Sent: 23 July 2004 05:00 To: FlightGear developers discussions Subject: RE: [Flightgear-devel] Latest OpenAL for new build? Jon Berndt writes: Right now we are relying on Norman Vine's OpenAL files. We must just hope that Norman can find the tme to update when and if required. The Makefile I used is in my tarball and the only changes I made in the code are in the header files also in the tarball Has that tarball been relocated? I tried downloading yours from teh link you posted a few months ago without success. Fred has a copy on his web site He posted a link, the other day when you were looking for it Note: You should be able to drop my tarball into a source tree then cd into the windows directory and issue a make command Not sure what you mean, exactly. Drop your tarball into an OpenAL source tree? Make, yes then make install? I don't know if I built the make install part or not There doesn't appear to be a make install part. Your files work for Cygwin as they are without the make/make install bit: what should they do? How do we update the files as OpenAl produces updated versions? Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest OpenAL for new build?
Hi, This one has me stumped. Downloaded the latest CVS version of OpenAL and did a build and install.. When compiling SimGear-0.3.6-pre2 get the following error in ../simgear/sound/opena1_test1.cxx ...openal_test1.cxx:113: undefined reference to 'alutLoadWavFile' ...openal_test1.cxx:125: undefined reference to 'alutUnloadWAV' walked thru the #ifdefs in alut.h and it looks like LINUX_AL is properly defined. Not all that conversant with the magic in automake and configure but neither program complains during the build process... Running with Debian woody and gcc-2.95.4 and automake 1.5 Any ideas, suggestions where to look.. Thanks John W ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest OpenAL for new build?
- Original Message - From: John Wojnaroski [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Friday, July 23, 2004 3:32 PM Subject: Re: [Flightgear-devel] Latest OpenAL for new build? Hi, This one has me stumped. Downloaded the latest CVS version of OpenAL and did a build and install.. When compiling SimGear-0.3.6-pre2 get the following error in ../simgear/sound/opena1_test1.cxx ...openal_test1.cxx:113: undefined reference to 'alutLoadWavFile' ...openal_test1.cxx:125: undefined reference to 'alutUnloadWAV' walked thru the #ifdefs in alut.h and it looks like LINUX_AL is properly defined. Not all that conversant with the magic in automake and configure but neither program complains during the build process... Running with Debian woody and gcc-2.95.4 and automake 1.5 Any ideas, suggestions where to look.. Okay, it was a earlier stale library (libopenal.so.0.0.6) left over from the Debian installation in /usr/lib while the openal make stuffs the lib file into /usr/local/lib/libopenal.so.0.0.7 Regards JW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest OpenAL for new build?
John Wojnaroski wrote: Trying a build of the latest pre-0.9.5 release... SimGear compile fails on sample_openal implicit declaration of alGetsourcei(...) and alutLoadWAVFile() Searched the include files for AL and there is an alGetsourceiv() and alGetSourcefv() but the above functions are missing. Running the stable version of debian (woody) and libopenal-dev 2.3 package from stable release. Searched thru the other testing and unstable directories with zero results... Does SimGear/FG require the latest versions from their OpenAL website? Probably yes, try grabbing the latest version from CVS. I was surprised to find that OpenAL has no official version number releases. You have to get the source via CVS if you get it from their site. And, they seem to be ok with making some API changes over time. And even stranger, they have a different API variant for MacOS. These are the annoyances we have to deal with when using OpenAL. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Latest OpenAL for new build?
On Thu, 22 Jul 2004 12:36:40 -0700 John Wojnaroski [EMAIL PROTECTED] wrote: Curtis L. Olson wrote: John Wojnaroski wrote: Trying a build of the latest pre-0.9.5 release... SimGear compile fails on sample_openal implicit declaration of alGetsourcei(...) and alutLoadWAVFile() Searched the include files for AL and there is an alGetsourceiv() and alGetSourcefv() but the above functions are missing. Running the stable version of debian (woody) and libopenal-dev 2.3 package from stable release. Searched thru the other testing and unstable directories with zero results... Does SimGear/FG require the latest versions from their OpenAL website? Probably yes, try grabbing the latest version from CVS. I was surprised to find that OpenAL has no official version number releases. You have to get the source via CVS if you get it from their site. And, they seem to be ok with making some API changes over time. And even stranger, they have a different API variant for MacOS. These are the annoyances we have to deal with when using OpenAL. Curt. Grabbed the latest CVS download from the OpenAl website and did a build and install. Things look okay.. Back to simgear There is no process like this for CygWin users, right? We have to use the pre-packaged tar file that exists somewhere on the net (I can't recall where it is). Have any CygWin users besides me, some months ago) tried to check out the latest OpenAL from CVS and compiling? Any time SimGear/FlightGear take advantage of new features added to OpenAL, CygWin users are going to have a problem, until OpenAL supports CygWin out of the box. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Latest OpenAL for new build?
-Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel- [EMAIL PROTECTED] On Behalf Of Jon S Berndt Sent: 22 July 2004 23:04 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Latest OpenAL for new build? On Thu, 22 Jul 2004 12:36:40 -0700 John Wojnaroski [EMAIL PROTECTED] wrote: Curtis L. Olson wrote: John Wojnaroski wrote: Trying a build of the latest pre-0.9.5 release... SimGear compile fails on sample_openal implicit declaration of alGetsourcei(...) and alutLoadWAVFile() Searched the include files for AL and there is an alGetsourceiv() and alGetSourcefv() but the above functions are missing. Running the stable version of debian (woody) and libopenal-dev 2.3 package from stable release. Searched thru the other testing and unstable directories with zero results... Does SimGear/FG require the latest versions from their OpenAL website? Probably yes, try grabbing the latest version from CVS. I was surprised to find that OpenAL has no official version number releases. You have to get the source via CVS if you get it from their site. And, they seem to be ok with making some API changes over time. And even stranger, they have a different API variant for MacOS. These are the annoyances we have to deal with when using OpenAL. Curt. Grabbed the latest CVS download from the OpenAl website and did a build and install. Things look okay.. Back to simgear There is no process like this for CygWin users, right? We have to use the pre-packaged tar file that exists somewhere on the net (I can't recall where it is). Have any CygWin users besides me, some months ago) tried to check out the latest OpenAL from CVS and compiling? Any time SimGear/FlightGear take advantage of new features added to OpenAL, CygWin users are going to have a problem, until OpenAL supports CygWin out of the box. Right now we are relying on Norman Vine's OpenAL files. We must just hope that Norman can find the tme to update when and if required. No sign yet of Cygwin recognizing OpenAL. Not a good situation. Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Latest OpenAL for new build?
Vivian Meazza writes: Right now we are relying on Norman Vine's OpenAL files. We must just hope that Norman can find the tme to update when and if required. The Makefile I used is in my tarball and the only changes I made in the code are in the header files also in the tarball Note: You should be able to drop my tarball into a source tree then cd into the windows directory and issue a make command HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Latest OpenAL for new build?
Vivian Meazza writes: Right now we are relying on Norman Vine's OpenAL files. We must just hope that Norman can find the tme to update when and if required. The Makefile I used is in my tarball and the only changes I made in the code are in the header files also in the tarball Has that tarball been relocated? I tried downloading yours from teh link you posted a few months ago without success. Note: You should be able to drop my tarball into a source tree then cd into the windows directory and issue a make command Not sure what you mean, exactly. Drop your tarball into an OpenAL source tree? Make, then make install? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Latest OpenAL for new build?
Jon Berndt writes: Right now we are relying on Norman Vine's OpenAL files. We must just hope that Norman can find the tme to update when and if required. The Makefile I used is in my tarball and the only changes I made in the code are in the header files also in the tarball Has that tarball been relocated? I tried downloading yours from teh link you posted a few months ago without success. Fred has a copy on his web site He posted a link, the other day when you were looking for it Note: You should be able to drop my tarball into a source tree then cd into the windows directory and issue a make command Not sure what you mean, exactly. Drop your tarball into an OpenAL source tree? Make, yes then make install? I don't know if I built the make install part or not Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
