Hi there, > >> It would also open some further possibilities, such as text-to-speech >> or pre-recorded messages. >> Drawback is, we would lose the portaudio driver. I don't know if Tat >> used that or openal on Mac, and no idea if any windows users managed >> to get fgcom running at all. > > I had in mind that the iaxc developers said they will be comptable to > Linux, OSX and Win. So I hope this will be the same for iaxc2. I will > set up a new branch for iaxc2 and will as Tat if he can check this
I compiled fgcom/iaxc1 using openal. I also tried iaxclient2 with iax-lofifilter branch. (PortAudio-V19(2.0), iaxclient/svn head, speex/svn head) After some (or I should say many) modifications in autotools/Xcode related things, I managed to build iaxclient2 and fgcom (only for intel) fgcom runs successfully with f910 option, so it probably runs on FlightGear mode too. To me, using PortAudio for iaxclient is no problem since PortAudio supports CoreAudio, an audio library for Mac OS, it's not that hard to build. just some configure tweaks and header file name replacements are required. One big issue in building iaxclient2 on Mac is that It can't make Universal binary due to option conflict (multipul arch options cannot be specified with -Mxxx options), which means I need to do something more on this. Another solution is to make an Xcode project for iaxclient2, but I don't want to maintain the Xcode project every time a file is added/removed. Anyway, Mac OS is ready to go for fgcom / iaxclient2 (of course with a lot of patches) Best, Tat ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
