Re: [Flightgear-devel] openAL compilation problem
bass pumped wrote: Hi, I'm trying to compile pre-rel-3 in MSVC 7 but i'm running into a linking problem again. It looks to me like simgear is unable to read the openAL header files while trying to link. I have put them in the sound_mngr directory and modified the include statements to read it directly from there, but with no luck. Am I doing something wrong? Thanks! Add the libs to FG, SG does not need them. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] openAL compilation problem
Add the libs to FG, SG does not need them. Harald. Hi Harald, Thank you for your reply. I did add the libraries to FG as you suggested but I still get the same errors. It looks like for some reason or the other the header files are not being read... for example the function alGetError is defined in al.h but even though the header file is included in soundmgr_openal.c the linker says that these are unresolved externals. Am I doing something wrong or is there something wrong with the version of openal I am using. I did download a copy of the openal windows sdk from the openal website. Thanks!! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
From: Jon Berndt [mailto:[EMAIL PROTECTED] I have placed a compiled tarball of yesterdays OpenAL CVS files @ http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz you might want to test these against the current FGFS before blindly overwriting your currrent installation Is this distribution modified for use with CygWin as discussed in this thread recently? Namely, the _WIN32 - WIN32 issue, as well as the #define MVC? I grabbed Norman Vine's tarball and have finally put sound into a Cygwin build. I noticed that there are still two instances of _WIN32 in the headers: One is in alu.h, and one is in alut.h. For example, in alu.h ... #ifdef _WIN32 #define ALUAPI #define ALUAPIENTRY __cdecl ... I don't know if these are intentional or by oversight. My first success was after changing the _WIN32 to WIN32 in those places. However, I cannot conclude that change was necessary due to other oversights along the way on my part. For example, one must make sure the openal32.dll used by fgfs.exe is the one distributed in Norman's tarball! Other OpenAL versions cause a runtime error. I was stuck on that one for awhile. :-) Thanks, everyone. Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
I have placed a compiled tarball of yesterdays OpenAL CVS files @ http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz you might want to test these against the current FGFS before blindly overwriting your currrent installation Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
I have placed a compiled tarball of yesterdays OpenAL CVS files @ http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz you might want to test these against the current FGFS before blindly overwriting your currrent installation Is this distribution modified for use with CygWin as discussed in this thread recently? Namely, the _WIN32 - WIN32 issue, as well as the #define MVC? I suspect these statements could be modified in OpenAL CVS to support CygWin without trouble. Has anyone approached them about this? If not, I wonder if I ought to? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OpenAL for CygWin
Jon Berndt wrote: I have placed a compiled tarball of yesterdays OpenAL CVS files @ http://www.vso.cape.com/~nhv/files/cygwin/cyg_openAL.tgz you might want to test these against the current FGFS before blindly overwriting your currrent installation Is this distribution modified for use with CygWin as discussed in this thread recently? Namely, the _WIN32 - WIN32 issue, as well as the #define MVC? I suspect these statements could be modified in OpenAL CVS to support CygWin without trouble. Has anyone approached them about this? If not, I wonder if I ought to? Previous patches (namely the complete IRIX backend) have been accepted without a problem (although you sometimes might need to ask for it a second time). Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Hmmm ... we had to fiddle with it to make it work some months ago ... I forget exactly what we did This seems really unfortunate for FlightGear - that we have to rely on another package where some of us have to fix the code to work for CygWin users. Is this even documented anywhere? jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt Hmmm ... we had to fiddle with it to make it work some months ago ... I forget exactly what we did This seems really unfortunate for FlightGear - that we have to rely on another package where some of us have to fix the code to work for CygWin users. Is this even documented anywhere? In the developers' list archives is the best we have. Cygwin wouldn't work at all if it were not for the excellent work by Norman Vine. There's no sign of OpenAL being ported to Cygwin at the moment, so this is the best we have. We are in constant danger of being left behind. Have you got it to work yet??? I guess I could tarball up my version here for you, when I have a bit more time. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
In the developers' list archives is the best we have. Cygwin wouldn't work at all if it were not for the excellent work by Norman Vine. There's no sign of OpenAL being ported to Cygwin at the moment, so this is the best we have. We are in constant danger of being left behind. Have you got it to work yet??? I guess I could tarball up my version here for you, when I have a bit more time. Yes. I now have a FlightGear executable - though I won't have time to try it until this evening at the earliest. I'd like to submit the text below to a FAQ or wherever it should be on the FlightGear/SimGear site: --- start --- For Cygwin users, OpenAL needs to be retrieved from this site: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz I placed this file in the /usr directory and untar'ed it, though some place it in the /usr/local/ directory tree - which might be more appropriate. Some library and dll files are untar'ed into your bin/ and lib/ subdirectories. Once the files are untar'ed, you must cd to the include/AL/ subdirectory and modify all the files where _WIN32 is present (use grep) and change it to simply WIN32 (that is, remove the underscore). Also, in alc.h you must change the code at top to look like this: #ifdef WIN32 --- CHANGE TO THIS #ifdef _OPENAL32LIB #define ALCAPI __declspec(dllexport) #else #define ALCAPI __declspec(dllimport) #endif #ifdef WIN32 --- CHANGE TO THIS typedef struct ALCdevice_struct ALCdevice; typedef struct ALCcontext_struct ALCcontext; #endif Once these changes are made, you should be able to compile simgear. --- end --- Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt In the developers' list archives is the best we have. Cygwin wouldn't work at all if it were not for the excellent work by Norman Vine. There's no sign of OpenAL being ported to Cygwin at the moment, so this is the best we have. We are in constant danger of being left behind. Have you got it to work yet??? I guess I could tarball up my version here for you, when I have a bit more time. Yes. I now have a FlightGear executable - though I won't have time to try it until this evening at the earliest. I'd like to submit the text below to a FAQ or wherever it should be on the FlightGear/SimGear site: --- start --- For Cygwin users, OpenAL needs to be retrieved from this site: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz I placed this file in the /usr directory and untar'ed it, though some place it in the /usr/local/ directory tree - which might be more appropriate. Some library and dll files are untar'ed into your bin/ and lib/ subdirectories. Once the files are untar'ed, you must cd to the include/AL/ subdirectory and modify all the files where _WIN32 is present (use grep) and change it to simply WIN32 (that is, remove the underscore). Also, in alc.h you must change the code at top to look like this: #ifdef WIN32 --- CHANGE TO THIS #ifdef _OPENAL32LIB #define ALCAPI __declspec(dllexport) #else #define ALCAPI __declspec(dllimport) #endif #ifdef WIN32 --- CHANGE TO THIS typedef struct ALCdevice_struct ALCdevice; typedef struct ALCcontext_struct ALCcontext; #endif Once these changes are made, you should be able to compile simgear. --- end --- Hmm ... I think we ought to correct the tarball first - we shouldn't ask people to correct it. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
For Cygwin users, OpenAL needs to be retrieved from this site: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz I placed this file in the /usr directory and untar'ed it, though some place it in the /usr/local/ directory tree - which might be more appropriate. Some library and dll files are untar'ed into your bin/ and lib/ subdirectories. Once the files are untar'ed, you must cd to the include/AL/ subdirectory and modify all the files where _WIN32 is present (use grep) and change it to simply WIN32 (that is, remove the underscore). Also, in alc.h you must change the code at top to look like this: #ifdef WIN32 --- CHANGE TO THIS #ifdef _OPENAL32LIB #define ALCAPI __declspec(dllexport) #else #define ALCAPI __declspec(dllimport) #endif #ifdef WIN32 --- CHANGE TO THIS typedef struct ALCdevice_struct ALCdevice; typedef struct ALCcontext_struct ALCcontext; #endif Once these changes are made, you should be able to compile simgear. I'm just in the middle of finally pulling an faq update together (various exams cropped up). I'll put this in. Are there any other issues people want to go in? Giles Robertson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt wrote: I'm finally getting around to reinstalling FlightGear after a hard drive crash a couple months ago. I have this as a place to get OpenAL for Cygwin: Try this version: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz Vivian I got that file. I untarred it in /usr, so the include files, libraries, etc. all went in the right places. However, I've tried building SimGear (under CygWin) and I get this error: --- start --- In file included from ../../simgear/sound/soundmgr_openal.hxx:50, from visual_enviro.cxx:33: /usr/include/AL/alc.h:39: error: syntax error before `*' token /usr/include/AL/alc.h:51: error: `ALCcontext' was not declared in this scope /usr/include/AL/alc.h:51: error: `alcHandle' was not declared in this scope /usr/include/AL/alc.h:51: error: variable `ALCboolean alcMakeContextCurrent' definition is marked dllimport. --- end --- Does anyone have any suggestions for me in configuring OpenAL to work with SimGear? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt Jon Berndt wrote: I'm finally getting around to reinstalling FlightGear after a hard drive crash a couple months ago. I have this as a place to get OpenAL for Cygwin: Try this version: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz Vivian I got that file. I untarred it in /usr, so the include files, libraries, etc. all went in the right places. However, I've tried building SimGear (under CygWin) and I get this error: --- start --- In file included from ../../simgear/sound/soundmgr_openal.hxx:50, from visual_enviro.cxx:33: /usr/include/AL/alc.h:39: error: syntax error before `*' token /usr/include/AL/alc.h:51: error: `ALCcontext' was not declared in this scope /usr/include/AL/alc.h:51: error: `alcHandle' was not declared in this scope /usr/include/AL/alc.h:51: error: variable `ALCboolean alcMakeContextCurrent' definition is marked dllimport. --- end --- Does anyone have any suggestions for me in configuring OpenAL to work with SimGear? Hmmm ... we had to fiddle with it to make it work some months ago ... I forget exactly what we did Here's some thoughts - might help. 1. I put my OpenAL stuff here: \usr\local\include\AL 2. Make sure there's no other openal stuff left around in other directories 3. Check that the appropriate lines in alc.h look exactly like this - there was a problem with underscores: #ifdef WIN32 #ifdef _OPENAL32LIB #define ALCAPI __declspec(dllexport) #else #define ALCAPI __declspec(dllimport) #endif #ifdef WIN32 typedef struct ALCdevice_struct ALCdevice; typedef struct ALCcontext_struct ALCcontext; #endif I think there was a problem elsewhere, but I can't identify it right now. If the lines are correct, then the other problem has likely been corrected as well. Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt wrote: I'm finally getting around to reinstalling FlightGear after a hard drive crash a couple months ago. I have this as a place to get OpenAL for Cygwin: http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz Is this still the latest/best dist? Try this version: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Vivian Meazza writes: Jon Berndt wrote: I'm finally getting around to reinstalling FlightGear after a hard drive crash a couple months ago. I have this as a place to get OpenAL for Cygwin: http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz Is this still the latest/best dist? I no longer have that file on my site Please delete any links to it and use this one instead Try this version: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz Thanks Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL / Cygwin
Note you will need a recent Cygwin DLL to use these this is untested http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz Norman: Is this file still online? Cape.com seems to think the site is offline or the file doesn't exist. Transient ISP problems? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL / Cygwin
Jon Berndt wrote: Note you will need a recent Cygwin DLL to use these this is untested http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz Norman: Is this file still online? Cape.com seems to think the site is offline or the file doesn't exist. Transient ISP problems? Maybe this is am alternative: http://the-agency.sourceforge.net/xoops/modules/mydownloads/visit.php?cid=5lid=49 Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
David Luff wrote: On a related note, I believe you had problems with hearing the ATIS voice due to low volume previously. Do you still have this problem post-OpenAL, or can you hear it OK now? I cannot hear the voice at all now, unfortunately. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
Curtis L. Olson wrote: It sounds ok to me here on my sound blaster live hardware. Can you hear the morse code beeps, marker beacons, or other sounds ok? Do some aircraft sound ok, or do all of them sound this way? The ident codes sound strange also (high-pitched and slow). All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
Matthew Law wrote: On my system (gentoo, SB Live 128) I hear what sounds like the turbine sample when at high angles of attack/sideslip and bank in the pa28-161. It's a very strange thing to hear in those situations and had me looking around at first to find the 'bogey'. Up to now in real fixed prop aircraft, I haven't heard the effect that Erik was trying to achieve... can this be heard outside the aircraft only? No. It can be heard from within the cabin also. But there is an effect that steps in at higher angles of attack, I'm just not sure how it really should sound like (I thought the current effect was quite close) and how to achieve that effect correctly. The easiest way to get it so the fly at cruise speed and pull back on the throttle and try to stay at altitude using the elevator. If the sound is heard in unusual situations, then that's because of a bug in the FDM. For one thing, I've heard someone say it is also there when parked on the ground. Obviously there should be no high alpha at such situations. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
Erik Hofman wrote: No. It can be heard from within the cabin also. But there is an effect that steps in at higher angles of attack, I'm just not sure how it really should sound like (I thought the current effect was quite close) and how to achieve that effect correctly. I'm not sure if what I'm hearing right now is an OpenAL library problem or a FlightGear problem, but it does not sound much like an airplane. The sound of a plane from inside the cabin is a very low, loud rumbling (or even roaring) sound -- it varies greatly by power, and very little (at least, I've never noticed) by angle of attack. On a plane with a constant speed propeller, the noise is much louder (and slightly higher-pitched) at high RPM. From the outside, the noise seems higher pitched than it does inside the cabin. If the sound is heard in unusual situations, then that's because of a bug in the FDM. For one thing, I've heard someone say it is also there when parked on the ground. Obviously there should be no high alpha at such situations. When you're parked on the ground, alpha can be just about anything, but since the relative wind is usually light to none, it doesn't matter much. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
On 5/24/04 at 10:44 AM David Megginson wrote: I'm not sure if what I'm hearing right now is an OpenAL library problem or a FlightGear problem, but it does not sound much like an airplane. The sound of a plane from inside the cabin is a very low, loud rumbling (or even roaring) sound -- it varies greatly by power, and very little (at least, I've never noticed) by angle of attack. On a plane with a constant speed propeller, the noise is much louder (and slightly higher-pitched) at high RPM. From the outside, the noise seems higher pitched than it does inside the cabin. If the sound is heard in unusual situations, then that's because of a bug in the FDM. For one thing, I've heard someone say it is also there when parked on the ground. Obviously there should be no high alpha at such situations. When you're parked on the ground, alpha can be just about anything, but since the relative wind is usually light to none, it doesn't matter much. On a related note, I believe you had problems with hearing the ATIS voice due to low volume previously. Do you still have this problem post-OpenAL, or can you hear it OK now? Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
David Luff wrote: On a related note, I believe you had problems with hearing the ATIS voice due to low volume previously. Do you still have this problem post-OpenAL, or can you hear it OK now? I haven't checked, because the engine audio is so intolerable (think dental drill) that I turn it off right away. I'll give it a try and see. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL question
David Megginson wrote: For at least a couple of weeks, the audio for the PA-28 or C172 on my Dell Inspiron notebook has sounded like an angry mosquito dying of tuberculosis. I think the problem started about the time of the switch to OpenAL (which I remember vaguely). I'm using the current Debian sid versions of libopenal0 and libopenal-dev (listed as 0.2003020200-1.2 in the DEB) under Linux 2.6.5, and would be grateful for any suggestions. It sounds ok to me here on my sound blaster live hardware. Can you hear the morse code beeps, marker beacons, or other sounds ok? Do some aircraft sound ok, or do all of them sound this way? 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] openal lib problem
Josh Babcock wrote: I just did my first recompile in a few months and everything seemed to build fine including openal, but at runtime I get this: [EMAIL PROTECTED] SimGear]$ fgfs fgfs: error while loading shared libraries: libopenal.so.0: cannot open shared object file: No such file or directory [EMAIL PROTECTED] SimGear]$ ls -l /usr/local/lib/*openal* -rwxr-xr-x1 root root 424510 May 6 17:09 /usr/local/lib/libopenal.a lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so - /usr/local/lib/libopenal.so.0.0.7 lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so.0 - /usr/local/lib/libopenal.so.0.0.7 -rwxr-xr-x1 root root 330457 May 6 17:09 /usr/local/lib/libopenal.so.0.0.7 Anybody know what I did wrong? I even ran a few of the tests, and they seemed to run fine. Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Oh, yeah SimGear and FlightGear were straight out of CVS this morning. Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] openal lib problem
Josh Babcock wrote: I just did my first recompile in a few months and everything seemed to build fine including openal, but at runtime I get this: fgfs: error while loading shared libraries: libopenal.so.0: cannot open shared object file: No such file or directory $ ls -l /usr/local/lib/*openal* lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so - /usr/local/lib/libopenal.so.0.0.7 Anybody know what I did wrong? Many distributions don't include /usr/local/lib on the default shared library path. Try setting it via an environment variable: export LD_LIBRARY_PATH=/usr/local/lib And see if that fixes the problem. If it does, then consider adding /usr/local/lib as a line in /etc/ld.so.conf (the global list of directories to search). Then you either need to run ldconfig or reboot to refresh the cache. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] openal lib problem
Josh, Add /usr/local/lib (or where ever you installed libopenal.so) to /etc/ld.so.conf and run ldconfig. Curt. Josh Babcock wrote: I just did my first recompile in a few months and everything seemed to build fine including openal, but at runtime I get this: [EMAIL PROTECTED] SimGear]$ fgfs fgfs: error while loading shared libraries: libopenal.so.0: cannot open shared object file: No such file or directory [EMAIL PROTECTED] SimGear]$ ls -l /usr/local/lib/*openal* -rwxr-xr-x1 root root 424510 May 6 17:09 /usr/local/lib/libopenal.a lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so - /usr/local/lib/libopenal.so.0.0.7 lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so.0 - /usr/local/lib/libopenal.so.0.0.7 -rwxr-xr-x1 root root 330457 May 6 17:09 /usr/local/lib/libopenal.so.0.0.7 Anybody know what I did wrong? I even ran a few of the tests, and they seemed to run fine. Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- 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] openal lib problem
Andy Ross wrote: Josh Babcock wrote: I just did my first recompile in a few months and everything seemed to build fine including openal, but at runtime I get this: fgfs: error while loading shared libraries: libopenal.so.0: cannot open shared object file: No such file or directory $ ls -l /usr/local/lib/*openal* lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so - /usr/local/lib/libopenal.so.0.0.7 Anybody know what I did wrong? Many distributions don't include /usr/local/lib on the default shared library path. Try setting it via an environment variable: export LD_LIBRARY_PATH=/usr/local/lib And see if that fixes the problem. If it does, then consider adding /usr/local/lib as a line in /etc/ld.so.conf (the global list of directories to search). Then you either need to run ldconfig or reboot to refresh the cache. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Thanks, I knew I was missing something simple. Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] openal lib problem
Josh Babcock said: Josh Babcock wrote: I just did my first recompile in a few months and everything seemed to build fine including openal, but at runtime I get this: [EMAIL PROTECTED] SimGear]$ fgfs fgfs: error while loading shared libraries: libopenal.so.0: cannot open shared object file: No such file or directory [EMAIL PROTECTED] SimGear]$ ls -l /usr/local/lib/*openal* -rwxr-xr-x1 root root 424510 May 6 17:09 /usr/local/lib/libopenal.a lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so - /usr/local/lib/libopenal.so.0.0.7 lrwxrwxrwx1 root root 33 May 6 17:09 /usr/local/lib/libopenal.so.0 - /usr/local/lib/libopenal.so.0.0.7 -rwxr-xr-x1 root root 330457 May 6 17:09 /usr/local/lib/libopenal.so.0.0.7 Anybody know what I did wrong? I even ran a few of the tests, and they seemed to run fine. Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Oh, yeah SimGear and FlightGear were straight out of CVS this morning. That openal install doesn't update your linker bindings. Just run ldconfig and the library will be found. That reminds me...it appears that there are no releases so to speak of openal. I could only find cvs. Anyone know more about this? Will this be an issue for our *nix users or do the latest distros all include some form of openal? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] openal lib problem
Curtis L. Olson said: Josh, Add /usr/local/lib (or where ever you installed libopenal.so) to /etc/ld.so.conf and run ldconfig. Curt. On my system the install just didn't do the binding step, but yeah if that isn't there ldconfig won't work anyway. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] openal lib problem
Jim Wilson wrote: That reminds me...it appears that there are no releases so to speak of openal. I could only find cvs. Anyone know more about this? Will this be an issue for our *nix users or do the latest distros all include some form of openal? I was a little dismayed to discover this too. I think the distros tend to just release a cvs snapshot can call it something like libopenal-2003020200 for the MMDDHH they did the check out. OpenAL definitely has some management annoyances. Other gripes are changes in the API between, uhhh, versions, and unexplainable API differences between platforms. But, it's got a lot to offer at the same time so I still think it's worth using. 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] OpenAL
David Luff helped some more -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Luff Sent: 28 April 2004 21:18 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] OpenAL Vivian Meazza writes: Result - failure, I downloaded openal.gz (not openal.tgz) and extracted the archive - no problems as far as I can see. Are you *sure* that your browser isn't mangling the file extension - it was a .tgz on Norman's web page when I checked 30 seconds ago. One of my browsers appends .gz to make it openal.tgz.gz, which is of course wrong. I renamed the file openal.tar.gz and extracted the files - seemed like it made no difference. I've downloaded the latest Simgear - compiles OK, no warnings. I've downloaded the latest FlightGear, made the changes. Configure reports with: Checking for library containing alGenBuffers ... No I also get this - don't worry about it! It's because the correct (Norman's) openal libs for cygwin aren't getting set in the configure script yet, so configure's tests can't possibly find them. Obviously this is something that will have to be fixed shortly. I thought that was likely. Then fails with Config.status: creating \ .infig.status: error:cannot find input file. It's possible that you haven't modified your src/Main/Makefile.am properly. All lines of fgfs_LDADD should have a \ at the end of them EXCEPT for the last line. Have you added a \ at the end of the last fgfs_LDADD line? Or removed one of the preceding ones. The space before each entry *must* be a tab I believe, not spaces. If *is* the src/Main Makefile.am you've modified yes, not the top-level one? If all else fails then remove the modified Makefile.am, recheck-out the original, make sure configure completes, and *then* modify it, and then you'll know its your mods that are the culprit if it fails again. I downloaded the most recent CVS version, with the modifications already made, and I still get Config.status: creating \ .infig.status: error:cannot find input file. I went back to the downloaded source code for 0.9.4 - that compiles OK. Any more ideas? A file locked up somewhere? Thanks for you help so far. Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Vivian Meazza writes: I downloaded the most recent CVS version, with the modifications already made, and I still get Config.status: creating \ .infig.status: error:cannot find input file. Hi Vivian, Was this a fresh CVS checkout or did you just refresh your existing files ? If the latter please do the following from your top level FlightGear source directory the one with the files from CVS % rm config*.* % cvs -z3 up -Pd % ./autogen.sh % ./configure % make If this doesn't work please ask again Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon Berndt writes: You need to re run configure before make I left this step out in my original msg :-( % ./configure % make % make test Norman I got a successful build. I tried running some of the also-successfully-built test programs: Nothing produced any sound. Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
On 4/28/04 at 4:10 AM Norman Vine wrote: Jon Berndt writes: You need to re run configure before make I left this step out in my original msg :-( % ./configure % make % make test Norman I got a successful build. I tried running some of the also-successfully-built test programs: Nothing produced any sound. Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz I've just tried it, and can't get it to link. I added -lopenal32 to the libraries in src/Main/Makefile.am, output is below: make[2]: Entering directory `/cvs_clean/FlightGear/src/Main' g++ -DPKGLIBDIR=\/Flightgear_clean/lib/FlightGear\ -Wall -O2 -D_REENTRANT -L/usr/local/lib -o fgf s.exe bootstrap.o ../../src/Main/libMain.a ../../src/Aircraft/libAircraft.a ../../src/ATC/libATC.a ../../src/Cockpit/libCockpit.a ../../src/Cockpit/built_in/libBuilt_in.a ../../src/Controls/libContro ls.a ../../src/FDM/libFlight.a ../../src/FDM/Balloon/libBalloon.a ../../src/FDM/ExternalNet/libExter nalNet.a ../../src/FDM/ExternalPipe/libExternalPipe.a ../../src/FDM/JSBSim/libJSBSim.a ../../src/FDM /YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a ../../src/FDM/LaRCsim/libLaRCsim.a . ./../src/FDM/UIUCModel/libUIUCModel.a ../../src/GUI/libGUI.a ../../src/Autopilot/libAutopilot.a ../. ./src/Input/libInput.a ../../src/Instrumentation/libInstrumentation.a ../../src/Model/libModel.a ../ ../src/AIModel/libAIModel.a ../../src/Network/libNetwork.a ../../src/Navaids/libNavaids.a ../../src/ Scenery/libScenery.a ../../src/Scripting/libScripting.a ../../src/Sound/libSound.a ../../src/Airport s/libAirports.a ../../src/MultiPlayer/libMultiPlayer.a ../../src/Replay/libReplay.a ../../src/System s/libSystems.a ../../src/Time/libTime.a ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel -lsgtiming -lsgio -lsgscreen -lsgmath -lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml -lsgsound -lsgserial -lsgstruct ure -lsgenvironment -lsgthreads -lpthread -lplibpu -lplibfnt -lplibjs -lplibnet -lplibssg -lplibsg -lplibul -lz -lopenal32 -lglut32 -lglu32 -lopengl32 -luser32 -lgdi32 ../../src/Input/libInput.a(input.o.b)(.text+0x3e81):input.cxx: undefined reference to `_joyGetDevCap [EMAIL PROTECTED]' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x19d):soundmgr_openal. cxx: undefined reference to `_alutInit' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x99d):soundmgr_openal. cxx: undefined reference to `_alutInit' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x111a):soundmgr_openal .cxx: undefined referenc e to `_alutExit' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x130a):soundmgr_openal .cxx: undefined referenc e to `_alutExit' /usr/local/lib/libsgsound.a(sample_openal.o)(.text+0x100a):sample_openal.cxx : undefined reference to `_alutLoadWAVFile' /usr/local/lib/libsgsound.a(sample_openal.o)(.text+0x1178):sample_openal.cxx : undefined reference to `_alutUnloadWAV' /usr/local/lib/libsgsound.a(sample_openal.o)(.text+0x1c0a):sample_openal.cxx : undefined reference to `_alutLoadWAVFile' /usr/local/lib/libsgsound.a(sample_openal.o)(.text+0x1d78):sample_openal.cxx : undefined reference to `_alutUnloadWAV' /usr/local/lib/libsgtiming.a(timestamp.o)(.text+0xd):timestamp.cxx: undefined reference to `_timeGet [EMAIL PROTECTED]' /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libplibjs.a(jsWindows.o)(.tex t+0x366):jsWindows.cxx: undefined reference to [EMAIL PROTECTED]' /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libplibjs.a(jsWindows.o)(.tex t+0x6e4):jsWindows.cxx: undefined reference to [EMAIL PROTECTED]' /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../libplibul.a(ulClock.o)(.text+ 0x91):ulClock.cxx: undef ined reference to [EMAIL PROTECTED]' collect2: ld returned 1 exit status make[2]: *** [fgfs.exe] Error 1 make[2]: Leaving directory `/cvs_clean/FlightGear/src/Main' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cvs_clean/FlightGear/src' make: *** [all-recursive] Error 1 My gcc version is 3.3.1-3 if that makes any difference: $ gcc -v Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/specs Configured with: /GCC/gcc-3.3.1-3/configure --with-gcc --with-gnu-ld --with-gnu-as --prefix=/usr --e xec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --libexecdir=/usr/sbin --mandir=/usr/share/man - -infodir=/usr/share/info --enable-languages=c,ada,c++,f77,pascal,java,objc --enable-libgcj --enable- threads=posix --with-system-zlib --enable-nls --without-included-gettext --enable-interpreter --enab le-sjlj-exceptions --disable-version-specific-runtime-libs --enable-shared --disable-win32-registry --enable-java-gc=boehm --disable-hash-synchronization --verbose --target=i686-pc-cygwin --host=i686- pc-cygwin --build=i686-pc-cygwin Thread model: posix gcc
Re: [Flightgear-devel] OpenAL
David Luff wrote: ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel -lsgtiming -lsgio -lsgscreen -lsgmath -lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml -lsgsound -lsgserial -lsgstruct ure -lsgenvironment -lsgthreads -lpthread -lplibpu -lplibfnt -lplibjs -lplibnet -lplibssg -lplibsg -lplibul -lz -lopenal32 -lglut32 -lglu32 -lopengl32 -luser32 -lgdi32 ../../src/Input/libInput.a(input.o.b)(.text+0x3e81):input.cxx: undefined reference to `_joyGetDevCap [EMAIL PROTECTED]' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x19d):soundmgr_openal. cxx: undefined reference Could you try moving -lopenal32 to the end of the linker command? As far as I know windows is a bit picky on the library sequence. Also, IRIX needs -laudio somewhere on the line, does Windows needs something similar? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Erik Hofman wrote: David Luff wrote: ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel -lsgtiming -lsgio -lsgscreen -lsgmath -lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml -lsgsound -lsgserial -lsgstruct ure -lsgenvironment -lsgthreads -lpthread -lplibpu -lplibfnt -lplibjs -lplibnet -lplibssg -lplibsg -lplibul -lz -lopenal32 -lglut32 -lglu32 -lopengl32 -luser32 -lgdi32 ../../src/Input/libInput.a(input.o.b)(.text+0x3e81):input.cxx: undefined reference to `_joyGetDevCap [EMAIL PROTECTED]' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x19d):soundmgr_openal. cxx: undefined reference Could you try moving -lopenal32 to the end of the linker command? As far as I know windows is a bit picky on the library sequence. Also, IRIX needs -laudio somewhere on the line, does Windows needs something similar? With MSVC, there is a library for ALut : ALut.lib. _joyGetDevCaps should be in winmm.lib -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Norman wrote: Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz -- test -- $ ./testdevice got Windows native audio -- test -- $ ./testmp3 boom.mp3 got Windows native audio chans 2 bps 16 bal 4 sps 44100 abs 176400 cbs 0 setfmt okay Could not GetProc alutLoadMP3_LOKI -- test -- $ ./testvorbis got Windows native audio chans 2 bps 16 bal 4 sps 44100 abs 176400 cbs 0 setfmt okay Could not GetProc alutLoadVorbis_LOKI -- test -- Many of the rest of them seemed to simply hang, but no sound was ever produced. I wonder, though, if your stuff was being used here, because I already have libopenal32.a in /usr/local/lib. I recompiled all the tests. Are we CygWin users going to be stuck with the previous codebase because openal doesn't work under CygWin? Or, do we have a choice with audio APIs? I'm hesitant to do a CVS update on the FlightGear tree at the moment because I'm not sure what the state of this OpenAL stuff is ... has it been formally introduced into FlightGear CVS, and does it replace the current audio system? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
On 4/28/04 at 7:17 AM Jon Berndt wrote: Many of the rest of them seemed to simply hang, but no sound was ever produced. I wonder, though, if your stuff was being used here, because I already have libopenal32.a in /usr/local/lib. I recompiled all the tests. The tests compile and link with ../src/libopenal.a, so unless you've hacked their build script or replaced that lib with Norman's then you'll still be linking (the tests) against the original. Are we CygWin users going to be stuck with the previous codebase because openal doesn't work under CygWin? Or, do we have a choice with audio APIs? I'm hesitant to do a CVS update on the FlightGear tree at the moment because I'm not sure what the state of this OpenAL stuff is ... has it been formally introduced into FlightGear CVS, and does it replace the current audio system? At the moment the current CVS won't compile on Cygwin - there is no option to use the old audio code (that I know of). This isn't a complaint though - I think the long term benefits should far outweigh the short term pain. Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On 4/28/04 at 2:13 PM Frederic Bouvier wrote: Erik Hofman wrote: David Luff wrote: ../../src/Environment/libEnvironment.a -lsgclouds3d -lsgrout e -lsgsky -lsgsound -lsgephem -lsgmaterial -lsgtgdb -lsgmodel -lsgtiming -lsgio -lsgscreen -lsgmath -lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml -lsgsound -lsgserial -lsgstruct ure -lsgenvironment -lsgthreads -lpthread -lplibpu -lplibfnt -lplibjs -lplibnet -lplibssg -lplibsg -lplibul -lz -lopenal32 -lglut32 -lglu32 -lopengl32 -luser32 -lgdi32 ../../src/Input/libInput.a(input.o.b)(.text+0x3e81):input.cxx: undefined reference to `_joyGetDevCap [EMAIL PROTECTED]' /usr/local/lib/libsgsound.a(soundmgr_openal.o)(.text+0x19d):soundmgr_openal . cxx: undefined reference Could you try moving -lopenal32 to the end of the linker command? As far as I know windows is a bit picky on the library sequence. Also, IRIX needs -laudio somewhere on the line, does Windows needs something similar? With MSVC, there is a library for ALut : ALut.lib. _joyGetDevCaps should be in winmm.lib OK, winmm fixes everthing except the alut stuff, I'm not sure why that broke right now but we've had that one before. The alut stuff is another matter - as far as I can tell only libopenal.a is built on Linux and that links OK, so why the trouble with Cygwin?. This is still the same link error I get with my own compile of the Linux subdir using Cygwin BTW. I hate linker errors - I always feel I have a fighting chance with compile errors, but I've never felt comfortable sorting linker errors :-( Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Norman Vine wrote: David Luff writes: On 4/28/04 at 4:10 AM Norman Vine wrote: Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz I've just tried it, and can't get it to link. I added -lopenal32 to the libraries in src/Main/Makefile.am, output is below: My WAG is you will need to add something like SoundLibs = -lopenal32 -lwinmm -ldsound -ldxguid -lole32 $(SoundLibs) There is a spot stubbed into the configure script for platform dependent audio libraries. Once we figure out exactly what we need for cygwin, we can put that into the configure script so it happens automatically. 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] OpenAL
David Luff writes: On 4/28/04 at 4:10 AM Norman Vine wrote: Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz I've just tried it, and can't get it to link. I added -lopenal32 to the libraries in src/Main/Makefile.am, output is below: My WAG is you will need to add something like SoundLibs = -lopenal32 -lwinmm -ldsound -ldxguid -lole32 $(SoundLibs) Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
On 4/28/04 at 1:29 PM David Luff wrote: On 4/28/04 at 7:17 AM Jon Berndt wrote: Many of the rest of them seemed to simply hang, but no sound was ever produced. I wonder, though, if your stuff was being used here, because I already have libopenal32.a in /usr/local/lib. I recompiled all the tests. The tests compile and link with ../src/libopenal.a, so unless you've hacked their build script or replaced that lib with Norman's then you'll still be linking (the tests) against the original. FWIW, the tests wouldn't link when I replaced src/libopenal.a with Norman's libopenal32.a (renamed to remove the '32'). Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Curtis L. Olson writes: Norman Vine wrote: David Luff writes: On 4/28/04 at 4:10 AM Norman Vine wrote: Have you tried my partial build of the openal / win directory http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz probably best to install this into /usr/local i.e. cd /usr/local tar -xzvf $PATH_TO/openal.tgz My WAG is you will need to add something like SoundLibs = -lopenal32 -lwinmm -ldsound -ldxguid -lole32 $(SoundLibs) There is a spot stubbed into the configure script for platform dependent audio libraries. Once we figure out exactly what we need for cygwin, we can put that into the configure script so it happens automatically. Note I am buried with *real* work and don't have any time for OpenSource for at least 2 weeks, but aren't there some test programs in SimGear someone can test this against ? Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On 4/28/04 at 1:33 PM David Luff wrote: On 4/28/04 at 2:13 PM Frederic Bouvier wrote: With MSVC, there is a library for ALut : ALut.lib. _joyGetDevCaps should be in winmm.lib OK, winmm fixes everthing except the alut stuff, I'm not sure why that broke right now but we've had that one before. The alut stuff is another matter - as far as I can tell only libopenal.a is built on Linux and that links OK, so why the trouble with Cygwin?. This is still the same link error I get with my own compile of the Linux subdir using Cygwin BTW. I hate linker errors - I always feel I have a fighting chance with compile errors, but I've never felt comfortable sorting linker errors :-( OK, I was wrong when I said it was the same as the original linker error. The original was undefined references to various __imp__* functions: ../../src/Cockpit/libCockpit.a(navcom.o)(.text+0xa404):navcom.cxx: undefined reference to `__imp__al GetError' ../../src/Cockpit/libCockpit.a(navcom.o)(.text+0xa70f):navcom.cxx: undefined reference to `__imp__al Sourcef' ../../src/Cockpit/libCockpit.a(navcom.o)(.text+0xa715):navcom.cxx: undefined reference to `__imp__al GetError' ../../src/Cockpit/libCockpit.a(marker_beacon.o)(.text+0x28c6):marker_beacon .cxx: undefined reference to `__imp__alSourcef' ../../src/Cockpit/libCockpit.a(marker_beacon.o)(.text+0x28d4):marker_beacon .cxx: undefined reference to `__imp__alGetError' ../../src/Cockpit/libCockpit.a(marker_beacon.o)(.text+0x2d32):marker_beacon .cxx: undefined reference to `__imp__alSourcef' ../../src/Cockpit/libCockpit.a(marker_beacon.o)(.text+0x2d40):marker_beacon .cxx: undefined reference to `__imp__alGetError' ' ...etc... Norman's libopenal32.a contains these functions, my libopenal.a doesn't, and these errors are hence fixed with Normans .a. However, Norman's libopenal32.a doesn't contain any alut* functions, which my libopenal.a does, so hence these errors are replaced with the _alut* errors. Norman, if you could tell us roughly how you created your libopenal32.a perhaps I could try creating one in the same manner but including the alut functions? Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On Wed, 28 Apr 2004 13:29:08 +0100 David Luff [EMAIL PROTECTED] wrote: The tests compile and link with ../src/libopenal.a, so unless you've hacked their build script or replaced that lib with Norman's then you'll still belinking (the tests) against the original. I'll have to adjust that. Has anyone gotten OpenAL to work with CygWin? I think the long term benefits should far outweigh the short term pain. ... for those _not_ using CygWin. For those using CygWin, it's fatal at the moment. Unfortunately, I have zero time to look into getting it working, with my workload on JSBSim, preparing for the conference later this summer, etc. So, at least at the moment, I'm stuck with the previous revision of Flightgear. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
David Luff writes: Norman's libopenal32.a contains these functions, my libopenal.a doesn't, and these errors are hence fixed with Normans .a. However, Norman's libopenal32.a doesn't contain any alut* functions, which my libopenal.a does, so hence these errors are replaced with the _alut* errors. Norman, if you could tell us roughly how you created your libopenal32.a perhaps I could try creating one in the same manner but including the alut functions? I have rebuilt the opeal dll and replaced the one on my site http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz This should export the required alut* funcs and it includes the Makefile I used Note you will need to use my headers instead of the ones in CVS if you want to recompile this easiest to do by % cd %OPEN_AL % tar -xzvf openal.tgz % cd win % make should just work the .a and .dll files will be left in the 'win' directory though My guess is we may need to add the Router / files to the DLL to take advantage of Vendor specific libraries but this will have to wait unless someone else wants to play Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon S Berndt writes: For those using CygWin, it's fatal at the moment. AFAICT It is fatal for those using any form of gcc on Win32. Oh well I guess there is always MSVC grin Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
On 4/28/04 at 10:09 AM Norman Vine wrote: I have rebuilt the opeal dll and replaced the one on my site http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz This should export the required alut* funcs and it includes the Makefile I used Note you will need to use my headers instead of the ones in CVS if you want to recompile this easiest to do by % cd %OPEN_AL % tar -xzvf openal.tgz % cd win % make should just work the .a and .dll files will be left in the 'win' directory though Norman, this compiles, links, and produces the expected sound from FlightGear :-) Many thanks for sorting this - I certainly couldn't have got it working otherwise. Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On 4/28/04 at 9:04 AM Jon S Berndt wrote: On Wed, 28 Apr 2004 13:29:08 +0100 David Luff [EMAIL PROTECTED] wrote: I think the long term benefits should far outweigh the short term pain. ... for those _not_ using CygWin. For those using CygWin, it's fatal at the moment. Norman's latest openal build fixes it :-) You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On Wed, 28 Apr 2004 15:57:55 +0100 David Luff [EMAIL PROTECTED] wrote: Norman, this compiles, links, and produces the expected sound from FlightGear :-) Many thanks for sorting this - I certainly couldn't have got it working otherwise. Cheers - Dave This was all done under CygWin? Can someone summarize the process? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
David Luff wrote: Norman's latest openal build fixes it :-) You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! In my own defense, all indications from the openal code and the web page seemed to be that cygwin was supported. I'm not able to test every combination of every platform in advance myself, especially since I don't have easy access to a windows machine that I can tie up to do cygwin builds ... or even has enough HD space if I wanted to. To be perfectly honest, the OpenAL switch has generally gone more smoothly than I expected. I was bracing for much worse, but most people on most platforms seemed to have an easy time of it. Cygwin is a little bit different nut to crack. As I understand it, cygwin can link against any .dll out there so in theory it should be able to work with the standard openal SDK. But, you have to create a wrapper libopenal.a to make the cygwin linker happy since it doesn't know how to directly link against .dll's. That process isn't all that difficult, but it also isn't documented very well and most people don't know how to do it. I remember fiddling with this stuff years ago when we first started this project because there wasn't any libopen*GL*.a for cygwin at that time, but I wouldn't be able to remember the details any more. Fortunately Norman pulled through with both the knowledge and the time to do this. Norman, is this something we should put on the FG web site, or bundle with simgear or something? 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] OpenAL
David Luff wrote: On 4/28/04 at 10:09 AM Norman Vine wrote: I have rebuilt the opeal dll and replaced the one on my site http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz This should export the required alut* funcs and it includes the Makefile I used Note you will need to use my headers instead of the ones in CVS if you want to recompile this easiest to do by % cd %OPEN_AL % tar -xzvf openal.tgz % cd win % make should just work the .a and .dll files will be left in the 'win' directory though Norman, this compiles, links, and produces the expected sound from FlightGear :-) Many thanks for sorting this - I certainly couldn't have got it working otherwise. *3 big cheers for Norman* 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] OpenAL
David Luff writes: On 4/28/04 at 10:09 AM Norman Vine wrote: I have rebuilt the opeal dll and replaced the one on my site http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz This should export the required alut* funcs and it includes the Makefile I used Note you will need to use my headers instead of the ones in CVS if you want to recompile this easiest to do by % cd %OPEN_AL % tar -xzvf openal.tgz % cd win % make should just work the .a and .dll files will be left in the 'win' directory though Norman, this compiles, links, and produces the expected sound from FlightGear :-) Cool ! Note this method should work with MingW32 also but one will need to recompile the libs and install them appropriately as the ones in my package are AFAICT Cygwin specific. Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On 4/28/04 at 10:09 AM Jon S Berndt wrote: This was all done under CygWin? Can someone summarize the process? Yes, under Cygwin. Here goes... Download Norman's prebuilt Cygwin openal from: http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz and place it somewhere, in this example in your home directory (~/). cd to /usr/local and extract the archive from there: tar xvfz ~/openal.tgz (the above assuming openal.tgz was in your home dir). Check out the latest SimGear and FlightGear - there have been recent matching changes. Build SimGear - if a test program fails to build in the sound dir then just remove it from the Makefile.am (ONLY if it's one of the test programs!!!). cd to the top level FlightGear dir. Modify FlightGear's src/Main/Makefile.am as follows: replace $(openal_LIBS) with -lopenal32 -lwinmm -ldsound -ldxguid -lole32 Hopefully this step should be removed in the near future when the configure script gets sorted for Cygwin. Build FlightGear, and report success or failure. Good luck! Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On Wed, 28 Apr 2004 16:00:20 +0100 David Luff [EMAIL PROTECTED] wrote: On 4/28/04 at 9:04 AM Jon S Berndt wrote: On Wed, 28 Apr 2004 13:29:08 +0100 David Luff [EMAIL PROTECTED] wrote: For those using CygWin, it's fatal at the moment. Norman's latest openal build fixes it :-) You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! This approach works only when there is a solution somewhere. From what I could tell in this case, that wasn't guaranteed - I was not confident that a viable fix would be found. My only development environment for Flightgear is CygWin. If that environment goes belly up, I'm toast. And sadly I don't have time to support any debugging efforts. I don't know who else uses CygWin exclusively, but I don't think there are many of us, so I get the feeling that the CygWin users don't have so much of a vote as the Linux guys. Thanks to Norman and yourself for getting to this point. Now will the build process integrate nicely with the normal FlightGear build procedure? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On 4/28/04 at 10:16 AM Curtis L. Olson wrote: David Luff wrote: Norman's latest openal build fixes it :-) You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! In my own defense, all indications from the openal code and the web page seemed to be that cygwin was supported. I'm not able to test every combination of every platform in advance myself, especially since I don't have easy access to a windows machine that I can tie up to do cygwin builds ... or even has enough HD space if I wanted to. Absolutely no defence is required :-) You've obviously put a lot of time and effort in to making this very worthwhile (IMHO) switch. To be perfectly honest, the OpenAL switch has generally gone more smoothly than I expected. I was bracing for much worse, but most people on most platforms seemed to have an easy time of it. Cygwin is a little bit different nut to crack. As I understand it, cygwin can link against any .dll out there so in theory it should be able to work with the standard openal SDK. But, you have to create a wrapper libopenal.a to make the cygwin linker happy since it doesn't know how to directly link against .dll's. That process isn't all that difficult, but it also isn't documented very well and most people don't know how to do it. I remember fiddling with this stuff years ago when we first started this project because there wasn't any libopen*GL*.a for cygwin at that time, but I wouldn't be able to remember the details any more. Fortunately Norman pulled through with both the knowledge and the time to do this. I guess the ideal situation as far as FlightGear is concerned would be if the openal binaries got bundled with Cygwin itself. Unfortunately I don't know nearly enough about how it fits together to confidently go on the Cygwin lists and advocate it. Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon S Berndt writes: You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! This approach works only when there is a solution somewhere. From what I could tell in this case, that wasn't guaranteed - I was not confident that a viable fix would be found. Nor was I, but usually one can find a way to compile Windows code with gcc but it often requires digging into the depths of the gnu linker documentation and studying the x86 specific link options for creating DLLs for WIN32. In this case the code depended on having both WIN32 and _WIN32 defined during compilation and the use of the link options -Wl,--export-all-symbols *.o $(LOCAL_PROJECT_LIBS) and -Wl,--no-whole-archive $(LIBS) which are LDs way of getting the proper linkage for symbols into a WIN32 DLL i.e. these export all local definitions and establish the 'thunks' to the imported definitions Judicous use of these flags along with compiling with the -mdll flag and linking with the -shared arguments to gcc usually results in being able to get a DLL built of course you still need to properly identify definitions with the usual DLLIMPORT DLLEXPORT macros but when compiling existing working WIN32 code you can almost always assume that this has always been done correctly. HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
David Luff writes: On 4/28/04 at 10:16 AM Curtis L. Olson wrote: Cygwin is a little bit different nut to crack. As I understand it, cygwin can link against any .dll out there so in theory it should be able to work with the standard openal SDK. This is only true for libraries with 'C' linkage, 'C++' linkage will *never* work unless the compilers concerned have a common ABI. But, you have to create a wrapper libopenal.a to make the cygwin linker happy since it doesn't know how to directly link against .dll's. works for 'C' libraries only That process isn't all that difficult, but it also isn't documented very well and most people don't know how to do it. Um.. this should help http://www.cygwin.com/cygwin-ug-net/dll.html I guess the ideal situation as far as FlightGear is concerned would be if the openal binaries got bundled with Cygwin itself. Unfortunately I don't know nearly enough about how it fits together to confidently go on the Cygwin lists and advocate it. Unfortunately I do not have the time to support the libraries I port so I do not submit them for inclusion with Cygwin but the official method of doing this is here http://cygwin.com/setup.html the-tech-part-is-done-making-it-point-and-clickable-I-leave-to-others'ly yr's Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On Wed, 28 Apr 2004 12:12:20 -0400 Norman Vine [EMAIL PROTECTED] wrote: Nor was I, but usually one can find a way to compile Windows code with gcc but it often requires digging into the depths of the gnu linker documentation and studying the x86 specific link options for creating DLLs for WIN32. I was also concerned about the hardware/driver interface issues, and how this would be built in a Unix-like environment. There was an ominous lack of mention of CygWin on the OpenAL site. Maybe the efforts here will be beneficial if fed back to the OpenAL project ... perhaps there's a FAQ entry in this somewhere for them. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Norman Vine wrote: Unfortunately I do not have the time to support the libraries I port so I do not submit them for inclusion with Cygwin but the official method of doing this is here http://cygwin.com/setup.html I suspect the OpenAL people should be the first ones to contact. I doubt the Cygwin folks will be interested in including a package until it builds out of the box on cygwin. Right now, the OpenAL win32 implementation (maintained by Creative, I believe) ships with a build environment for MSVC only. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Andy Ross writes: Norman Vine wrote: Unfortunately I do not have the time to support the libraries I port so I do not submit them for inclusion with Cygwin but the official method of doing this is here http://cygwin.com/setup.html I suspect the OpenAL people should be the first ones to contact. I doubt the Cygwin folks will be interested in including a package until it builds out of the box on cygwin. Right now, the OpenAL win32 implementation (maintained by Creative, I believe) ships with a build environment for MSVC only. It is not uncommon to have specific Cygwin mods for packages shipped with Cygwin. In fact this is the norm. Instructions for how to package these are on the Cygwin link I posted in my earlier message. Of course if Creative wants to support gcc on WIN32 this would be best but I won't hold my breath Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
David Luff gave clear instructions On 4/28/04 at 10:09 AM Jon S Berndt wrote: This was all done under CygWin? Can someone summarize the process? Yes, under Cygwin. Here goes... Download Norman's prebuilt Cygwin openal from: http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz and place it somewhere, in this example in your home directory (~/). cd to /usr/local and extract the archive from there: tar xvfz ~/openal.tgz (the above assuming openal.tgz was in your home dir). Check out the latest SimGear and FlightGear - there have been recent matching changes. Build SimGear - if a test program fails to build in the sound dir then just remove it from the Makefile.am (ONLY if it's one of the test programs!!!). cd to the top level FlightGear dir. Modify FlightGear's src/Main/Makefile.am as follows: replace $(openal_LIBS) with -lopenal32 -lwinmm -ldsound -ldxguid -lole32 Hopefully this step should be removed in the near future when the configure script gets sorted for Cygwin. Build FlightGear, and report success or failure. Good luck! Cheers - Dave Result - failure, I downloaded openal.gz (not openal.tgz) and extracted the archive - no problems as far as I can see. I've downloaded the latest Simgear - compiles OK, no warnings. I've downloaded the latest FlightGear, made the changes. Configure reports with: Checking for library containing alGenBuffers ... No Then fails with Config.status: creating \ .infig.status: error:cannot find input file. I think that this failure may have nothing to do with openAL, but I can't see what's wrong. My knowledge of Cygwin is vestigial. FlightGear-0.9.4 compiles without error. Any pointers? Regards Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
David Luff wrote: You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! He has proven to be a good student :-D Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Vivian Meazza writes: Result - failure, I've downloaded the latest FlightGear, made the changes. Configure reports with: Ah, you shouldn't need the src/Main/Makefile.am changes anymore, Curt has added the libs to configure.ac already. Remove your src/Main/Makefile.am, recheckout and see if that works. Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Erik Hofman writes: David Luff wrote: You have to admire Curt's methodology - fatally breaking the Cygwin build has certainly created a momentum to fix it, and presumably saved the time and hassle of riddling the sound code with ifdefs! He has proven to be a good student :-D Just curious - Has anyone gotten SDL working with Cygwin yet ? Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
David Luff wrote: Vivian Meazza writes: Result - failure, I downloaded openal.gz (not openal.tgz) and extracted the archive - no problems as far as I can see. Are you *sure* that your browser isn't mangling the file extension - it was a .tgz on Norman's web page when I checked 30 seconds ago. One of my browsers appends .gz to make it openal.tgz.gz, which is of course wrong. I can confirm that : Internet Explorer is doing strange thing with Norman's link. It becomes openal.gz and the tar file is not accessible after decompression. Mozilla is fine. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon, I have *no* idea if it actually produces any sound as I don't have a sound board on my development system but after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal then % cd $OPENAL % cd linux % ./autogen.sh I got this after running autogen.sh: configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:256: warning: AC_TRY_RUN called without default to allow cross compiling ... and then make totally cratered. % make % make test Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon Berndt writes: I have *no* idea if it actually produces any sound as I don't have a sound board on my development system but after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal then % cd $OPENAL % cd linux % ./autogen.sh I got this after running autogen.sh: configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:256: warning: AC_TRY_RUN called without default to allow cross compiling ... and then make totally cratered. You need to re run configure before make I left this step out in my original msg :-( % ./configure % make % make test Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
On 27 Apr 2004 at 7:23, Jon Berndt wrote: Jon, I have *no* idea if it actually produces any sound as I don't have a sound board on my development system but after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal then % cd $OPENAL % cd linux % ./autogen.sh I got this after running autogen.sh: configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:256: warning: AC_TRY_RUN called without default to allow cross compiling ... and then make totally cratered. I also got that output from autogen.sh, also on Linux - it appears to be harmless. Make went fine on Cygwin. No audio output from the test programs on Cygwin though :-( Haven't managed to get FlightGear to link to it on Cygwin yet either. As you say, googling OpenAL and Cygwin appears to find sweet FA. Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
David Luff wrote: I also got that output from autogen.sh, also on Linux - it appears to be harmless. Make went fine on Cygwin. No audio output from the test programs on Cygwin though :-( It's important to point out that the linux/src/arch/windows directory in the OpenAL source distribution is very much *not* the same code as you will find in the win directory (or in the OpenAL32.dll you can get from the NVidia or Creative SDKs). It looks like an older and/or alternative (or maybe incomplete) implementation. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Because of the FG/OpenAL/Cygwin problem, I'm trying to get FG to compile using Msys and mingw. (This doesn't hold out a huge amount of hope, as msys is a cygwin fork, but, we might get somewhere). Does anybody have any instructions on this? (I don't want to sink large amounts of time if somebody's already done it) Giles Robertson -Original Message- From: D Luff [mailto:[EMAIL PROTECTED] Sent: 27 April 2004 12:47 To: FlightGear developers discussions Subject: RE: [Flightgear-devel] OpenAL On 27 Apr 2004 at 7:23, Jon Berndt wrote: Jon, I have *no* idea if it actually produces any sound as I don't have a sound board on my development system but after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal then % cd $OPENAL % cd linux % ./autogen.sh I got this after running autogen.sh: configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:147: warning: AC_TRY_RUN called without default to allow cross compiling configure.in:256: warning: AC_TRY_RUN called without default to allow cross compiling ... and then make totally cratered. I also got that output from autogen.sh, also on Linux - it appears to be harmless. Make went fine on Cygwin. No audio output from the test programs on Cygwin though :-( Haven't managed to get FlightGear to link to it on Cygwin yet either. As you say, googling OpenAL and Cygwin appears to find sweet FA. Cheers - Dave This message has been scanned but we cannot guarantee that it and any attachments are free from viruses or other damaging content: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL / Cygwin
No idea if this will work or not but here is a binary OpenAL distribution of the core OpenAL files from the win directory Note you will need a recent Cygwin DLL to use these this is untested http://www.vso.cape.com/~nhv/files/fgfs/openal.tgz HTH Norman EXPORTS EAXGet @1 EAXSet @2 alBufferData @3 alDeleteBuffers @4 alDeleteSources @5 alDisable @6 alDistanceModel @7 alDopplerFactor @8 alDopplerVelocity @9 alEnable @10 alGenBuffers @11 alGenSources @12 alGetBoolean @13 alGetBooleanv @14 alGetBufferf @15 alGetBufferi @16 alGetDouble @17 alGetDoublev @18 alGetEnumValue @19 alGetError @20 alGetFloat @21 alGetFloatv @22 alGetInteger @23 alGetIntegerv @24 alGetListener3f @25 alGetListenerf @26 alGetListenerfv @27 alGetListeneri @28 alGetProcAddress @29 alGetSource3f @30 alGetSourcef @31 alGetSourcefv @32 alGetSourcei @33 alGetString @34 alIsBuffer @35 alIsEnabled @36 alIsExtensionPresent @37 alIsSource @38 alListener3f @39 alListenerf @40 alListenerfv @41 alListeneri @42 alSource3f @43 alSourcePause @44 alSourcePausev @45 alSourcePlay @46 alSourcePlayv @47 alSourceQueueBuffers @48 alSourceRewind @49 alSourceRewindv @50 alSourceStop @51 alSourceStopv @52 alSourceUnqueueBuffers @53 alSourcef @54 alSourcefv @55 alSourcei @56 alcCloseDevice @57 alcCreateContext @58 alcDestroyContext @59 alcGetContextsDevice @60 alcGetCurrentContext @61 alcGetEnumValue @62 alcGetError @63 alcGetIntegerv @64 alcGetProcAddress @65 alcGetString @66 alcIsExtensionPresent @67 alcMakeContextCurrent @68 alcOpenDevice @69 alcProcessContext @70 alcSuspendContext @71 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
You need to re run configure before make I left this step out in my original msg :-( % ./configure % make % make test Norman I got a successful build. I tried running some of the also-successfully-built test programs: --start-- $ ./testpitch2 got Windows native audio chans 2 bps 16 bal 4 sps 44100 abs 176400 cbs 0 setfmt okay note E beats 9 no sound --end-- Nothing produced any sound. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL breaks voice ATIS
David Luff wrote: Hi folks, The recent OpenAL change has broken voice ATIS (start up the default Cessna at KSFO and transfer the 118.85 standby freq on comm1 to be active - the program will segfault) and I can't seem to figure out a fix on my own. The segfault occurs in ATCVoice.cxx line 172, which is memcpy. This is copying sections from the original voice data buffer to make up a new custom data buffer containing the message. My first thought was that the rawSoundData buffer was getting deleted behind my back, so I modified LoadVoice to copy the buffer obtained from openal (patch at end of mail - don't apply this!). However, this now dies at the new memcpy line in LoadVoice. The rawDataSize returned from the sound sample is correct according to a quick check with a hex editor, so I can only conclude that the memory address returned by get_data() from the sound sample is not that of the data, or that it's been deleted by the sample before I call get_data()? Any thoughts on this - I'm somewhat out of ideas. Ooops, you are right, I didn't test ATIS voice when I switched to OpenAL. Yes, the way openal works is you call a function to load the wav file, then you call a function that buffers it internally to openal, then you call a function that cleans up (which delete the in memory copy you have access to.) I updated the sound_sample api to allow you to request that this in memory version not be immediately cleaned up, but instead be deleted when the sound sample destructor is called. This is less efficient memory-wise, but gives you optional access to the raw data for those times when you want to manipulate it. Regards, 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] OpenAL update
Curtis L. Olson wrote: Frederic Bouvier wrote: What is the right way to exit the main loop, rather than just calling exit() ? If there is no other option, we need an atexit call. I put alutExit() before exit(), with a sample playing from a previous run and the sound created by this instance are shut, the program stop as expected and my crazy sample is still playing. Rebooting once again... Fred, I added an atexit() function to CVS that deletes the global class. This should then also delete the soundmgr class which will cause alutExit() to be called. This might also give us the opportunity to hook in the SDL cleanup function as well. That works well, either by asking to exit in the menu, or closing the window. Destroying the samples kill the sound, alutExit just cleaning a quiet process. I'll have to remember not to kill fg or interrupt a debugging session. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL runtime error
Flightgear and Simgear builds ok on SuSE Linux 9.0, but when I try to run Flightgear I get this error message: I'm also running SuSE 9.0 with the same default openal packages. Initializing OpenAL sound manager fgfs: pcm.c:1050: snd_pcm_writei: Assertion `pcm-setup' failed. I don't get this message. I do get sound and an openal message 'Initializing OpenAL sound manager'. Maybe something else is using the sound device? Chris. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL runtime error
On Sunday 25 April 2004 12:49, Chris Horler wrote: Flightgear and Simgear builds ok on SuSE Linux 9.0, but when I try to run Flightgear I get this error message: I'm also running SuSE 9.0 with the same default openal packages. I have VT8233/A/8235 AC97 Audio Controller that's a mainboard-integrated soundcard. Initializing OpenAL sound manager fgfs: pcm.c:1050: snd_pcm_writei: Assertion `pcm-setup' failed. I don't get this message. I do get sound and an openal message 'Initializing OpenAL sound manager'. Maybe something else is using the sound device? I did try to run twm instead of KDE to make sure that KDE was not useing the sound device, but I got the same error. I've also tried the orbz demo (a game) that is supposed to use OpenAL. That worked fine (under KDE), so I guess that there is nothing wrong with: sound device, alsa, openal. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Jon Berndt writes: Jon, you might also search for libopenal along with cygwin ... if cygwin packaged openal, I bet that is what they'd call it. Curt. That search appeared to be more productive initially, but nothing helpful has cropped up, yet. Jon, CygWin user - Help, Help! I'm being repressed! Jon, I have *no* idea if it actually produces any sound as I don't have a sound board on my development system but after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal then % cd $OPENAL % cd linux % ./autogen.sh % make % make test compiles everything without a complaint on my Cygwin installation HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Norman Vine wrote: after getting the OPENAL CVS files cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository login (use password guest) cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal OOPS I forgot the configure command then % cd $OPENAL % cd linux % ./autogen.sh % ./configure % make % make test compiles everything without a complaint on my Cygwin installation HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
I tried essentially what you suggested yesterday. I'll try again later today, but following your explicit example. If needed I may re-checkout the distro. I'll let you know what I get. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Under Gentoo: emerge openal then it built fine against CVS Simgear however I'm having trouble getting autogen.sh to pick everything up correctly for building CVS FlightGear. Is anyone here running CVS FlightGear under Gentoo? If not I may have to look into how to construct an ebuild for portage. Cheers, Al ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL
Some feedback on OpenAL: I just updated plib, SimGear, and FlightGear from cvs. With the default Cessna 172, the sound does not change with throttle setings or RPM change. Also, the ident for the ADF does not go away when I turn off the ident or change frequencies. The flap motion sounds and the touchdown and runway sounds seem normal. The outer marker, middle marker, and inner marker sounds were normal. I continually get the following error: Oops AL error in sample set_volume()! I am running an current Suse 9.0 Professional with default OpenAL (kernel 2.4.21-202). I tried several other AC and did hear a change with the throttle for the hunter, but still get the ame repeating error. Is anyoune else seeing similar errors? Dave Perry ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
On Sunday 25 April 2004 23:31, Dave Perry wrote: Some feedback on OpenAL: I just updated plib, SimGear, and FlightGear from cvs. With the default Cessna 172, the sound does not change with throttle setings or RPM change. Also, the ident for the ADF does not go away when I turn off the ident or change frequencies. That is likely because the kr-87 adf is also active but it does not have a instrument panel in the default C172. You can turn it off through the property browser. So, bottom line: this is not a OpenAL problem. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Curtis L. Olson wrote: 3. The maximum pitch factor that OpenAL allows is 2.0 ... we blow by that with some of our sound configs ... that's another thing that will need to be tweaked and looked at. We can do the down-sampling manually and choose the right one at runtime; basically mipmapping the audio data. This wouldn't be too hard. Then again, do we really need more than two octaves of pitch shift or is this just an artifact of poor frequency choice in the original sample? Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Andy Ross wrote: Curtis L. Olson wrote: 3. The maximum pitch factor that OpenAL allows is 2.0 ... we blow by that with some of our sound configs ... that's another thing that will need to be tweaked and looked at. We can do the down-sampling manually and choose the right one at runtime; basically mipmapping the audio data. This wouldn't be too hard. Then again, do we really need more than two octaves of pitch shift or is this just an artifact of poor frequency choice in the original sample? Looking at the default c172 engine sound. It is a 22000 hz sample. However, plib was playing this at 8000 hz. So we had to specify a pitch of 2.75 just to get it back up to normal speed. This stuff is built into the sound config.xml, but when we use the same config file with openal, the pitch comes out 2.75x too high so we will need to track down these situations and fix them in the config file. That should get us back within reasonable range. I doubt we would need more than 2 octaves, although we can go significantly less than 1.0 so that gives us quite a bit of range. One thing that I've always wanted to do is set things up so we can sample then engine at different rpm's and then have the system transition between them (with appropriate blending) as the engine speed changes. We didn't push this originally, because in the early days, plib only supported 3 concurrent sounds and we had other things to spend our 3 sample budget on. Regards, 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] OpenAL
Wouldn't it be possible to record an engine sound at low RPM and change the pitch using codes? Regards, Ampere On April 24, 2004 11:54 am, Curtis L. Olson wrote: One thing that I've always wanted to do is set things up so we can sample then engine at different rpm's and then have the system transition between them (with appropriate blending) as the engine speed changes. We didn't push this originally, because in the early days, plib only supported 3 concurrent sounds and we had other things to spend our 3 sample budget on. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Ampere K. Hardraade wrote: Wouldn't it be possible to record an engine sound at low RPM and change the pitch using codes? Sure, and that works ok, but I bet if you record the engine at different rpms you will discover that doubling the pitch of a sample recorded at 1000 rpm will not sound as much like the actual engine running at 2000 rpm as you would have hoped ... What you suggest is what we are doing now. We have one engine sample that is played over the entire RPM range, but we could improve our sound quality if we did the work to blend different samples for different rpm ranges ... Regards, 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] OpenAL update
I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the I didn't see a CygWin platform listed for OpenAL on their web site (openal.org). I also didn't see mention of Cygwin here: http://developer.creative.com/landing.asp?cat=1sbcat=31top=38. I wonder if I simply download the source if I can compile it ... there's an experiment waiting for a developer. I'd do it, but the weather is turning nice (http://instacam.com/instacamimg/KEMAH/KEMAH_s.jpg - just up the street overlooking Galveston Bay, tonight's dinner destination), so I'm going outside with the family. This OpenAL thing has got me a little uneasy, being a CygWin user, but the benefits look real good. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: I am going to commit my OpenAL changes to SimGear and FlightGear this afternoon. I haven't seen even one negative comment on OpenAL since I first brought this topic up several days ago ... so hopefully everyone is on board with this change. I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the configure script assumes we want to link with -lopenal, but I don't expect this to work right for every platform. I expect there may be a couple days of head aches here while we get these platform dependent differences ironed out. Please be patient! I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. Regards, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. Hmmm, I wonder if I'm not doing the exit stuff correctly. This problem doesn't happen on Linux, but linux maybe better at cleaning up wayward processes? 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] OpenAL update
Curtis L. Olson wrote: Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. It doesn't look like the sound manager destructor is ever getting called. This should happen inside of the globals destructor, but that is never getting called either. I don't think any one has paid much attention to cleanup and exiting from FG, but we may need to address this now. Do we need an atexit() function that will clean things up for us? Curt. 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] OpenAL update
Curtis L. Olson wrote: Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. Hmmm, I wonder if I'm not doing the exit stuff correctly. This problem doesn't happen on Linux, but linux maybe better at cleaning up wayward processes? The OpenAl Programmer's guide says one must call alutExit before exiting. alutExit is in the destructor of SGSoundMgr, but AFAICS the manager is not destroyed at shutdown time. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL update
Curtis L. Olson wrote: Curtis L. Olson wrote: Frederic Bouvier wrote: I updated and compiled FG with OpenAL flawlessly. Before I downloaded the Creative SDK for OpenAL and installed it. The headers are not in an AL/ directory, just Include, so I created this folder and moved the files to it. I added the path to the headers and the libraries in the IDE and libraries 'OpenAL32.lib ALut.lib' in the flightgear project file. I was going to report a success because I was able to ear 3 samples at the same time, but fgfs was unable to stop when I hit ESC then confirm by clicking OK. The program just hang with the sound still playing. I killed the program but the sounds are still here. I also restart FG in the hope it will kill sound at init but they are still here and rehang and rekill. I will need to reboot to stop that ILS marker that make me crazy. It doesn't look like the sound manager destructor is ever getting called. This should happen inside of the globals destructor, but that is never getting called either. I don't think any one has paid much attention to cleanup and exiting from FG, but we may need to address this now. Do we need an atexit() function that will clean things up for us? What is the right way to exit the main loop, rather than just calling exit() ? If there is no other option, we need an atexit call. I put alutExit() before exit(), with a sample playing from a previous run and the sound created by this instance are shut, the program stop as expected and my crazy sample is still playing. Rebooting once again... -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL - http://www.openal.org
Dave wrote: Thanks for the feedback. I was hoping to catch up with you after you'd finished flying and discover what you thought of the helicopter dynamics, but missed you. I guess we've got some serious improvement to do. If you fly our helicopters occaisionally and tell us what is good and bad about the modelling that would be fantastic - I'm not aware of any other real-life heli pilots on the list. What heli is it you fly in real-life by the way? Cheers - Dave R22 /R44 for instructing and Bell 47 for air displays and fun. Lapsed turbine rating too. - Tracy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] OpenAL update
I need help though from the Mac people and cygwin/mingwin people. What are the openal libraries called on these platforms. At the moment the configure script assumes we want to link with -lopenal, but I don't expect this to work right for every platform. I expect there may be a couple days of head aches here while we get these platform dependent differences ironed out. Please be patient! Has anyone seen reference to the use of OpenAL with CygWin anywhere? I downloaded it, and tried configuring the linux subdirectory to build under cygwin - no joy (yet, at least). The Windows directory is so far a bit of a mystery, but there is no mention of cygwin there, either. I did a google search but so far have not found the words cygwin and openal together in a meaningful web page. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Hello Curt, will this require an OpenAL (dev) package to be installed, or will everything needed be included in the FG source? LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Lee Elliott wrote: Hello Curt, will this require an OpenAL (dev) package to be installed, or will everything needed be included in the FG source? Yes, you'll want the openal dev package (or sdk or whatever it is called for your platform.) 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] OpenAL update
Jon, I did a google search but so far have not found the words cygwin and openal together in a meaningful web page. http://cvs.seul.org/cgi-bin/cvsweb-1.80.cgi/games/openal/linux/configure.in This looks like it could be the openal cvs source tree (I don't have it to check). If you search for cygwin on this page it says 'fixes for cygwin builds, that might mean someone has tried it at some stage. Chris. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] OpenAL
Lee Elliott wrote: will this require an OpenAL (dev) package to be installed, or will everything needed be included in the FG source? It will require OpenAL to be installed separately. I just did it under linux, and it's a relatively benign ./autogen.sh ./configure make make install kind of thing. They imply that some distributions install it by default (Fedora doesn't), so it may already be there. The win directory seems to be MSVC specific, so Jon's fears about a cygwin build are probably justified (the linux directory won't build in cygwin: you want the Win32/DirectX implementation, not the OSS/ALSA one). There is a link to a binary SDK available from Creative, though, so presumably cygwin users could use that? I believe cygwin can link programs against normal windows .lib files, right? Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
