Re: [Flightgear-devel] FlightGear voice communication

Hi Dirk, Thanks you for your feedback ! I will try to bring you some answer. - bandwith: Indeed IAXClient has a function called void iaxc_set_silence_threshold(float thr); unfortunately, looking at source code this function does exactly the same as we are doing in FGCom source code : set input_

Re: [Flightgear-devel] FlightGear voice communication

nice to see fgcom stepping forward. Installing the fgcom-server(delta384) was my first touch with Asterisk, amassing power full tool. Looking back see a lot of bandwith. my suggestions for improvement: - bandwith : the fgcom-client(iax) didn't close upstream only the mic, i have deep in mind

Re: [Flightgear-devel] 2.12 is branched

Hi Gijs, Yes, it certainly 'looks' that way ;=() I just did a git pull, and I can only produce that SAME link error in my Windows 7 build if I comment out the line - list(APPEND PLATFORM_LIBS "winmm.lib") Then I get what you showed - SimGearCored.lib(timestamp.obj) : error LNK2019: unresolve

Re: [Flightgear-devel] 2.12 is branched

Hi Geoff, > That can be fixed by adding Winmm.lib to the link... Fred already did that some time ago, right? https://www.gitorious.org/fg/fgrun/commit/d25fad49b73f51459ef2bdaa7e040da8259a02a0 Cheers, Gijs

Re: [Flightgear-devel] 2.12 is branched

Hi Gijs, That can be fixed by adding Winmm.lib to the link... Like in the fgrun CMakeLists.txt file add - target_link_libraries( fgrun Winmm ) Regards, Geoff. On Thu, 2013-08-15 at 12:54 +0200, Gijs de Rooy wrote: > It seems to fail on building FGRun.exe: > SimGearCore.lib(timestamp.obj) : erro

Re: [Flightgear-devel] 2.12 is branched

It seems to fail on building FGRun.exe: SimGearCore.lib(timestamp.obj) : error LNK2019: unresolved external symbol __imp__timeGetTime@0 referenced in function "public: void __thiscall SGTimeStamp::stamp(void)" (?stamp@SGTimeStamp@@QAEXXZ) FGRun-Win64-Cmake also fails (unrelated to this release is

Re: [Flightgear-devel] 2.12 is branched

On 15 Aug 2013, at 10:50, Gijs de Rooy wrote: > Is http://flightgear.simpits.org:8080/job/Windows-release/ the build that we > should look at? Correct. James -- Get 100% visibility into Java/.NET code with AppDynamics

Re: [Flightgear-devel] 2.12 is branched

Hi James, > James wrote: > the biggest obstacle to an RC is getting the Windows build slaves to behave; > if anyone on Windows could look at the Jenkins logs and shed any light, it > would help. Is http://flightgear.simpits.org:8080/job/Windows-release/ the build that we should look at? Cheers,

Re: [Flightgear-devel] New release date for 2.12

On 15 Aug 2013, at 09:46, Torsten Dreyer wrote: > Curt and James, what would you think about publishing the release during the > weekend > Sept. 14./15.? Or would you prefer to stick to the 17th (a Tuesday)? I'm actually returning from a weeks holiday that weekend, so the Tuesday is better.

Re: [Flightgear-devel] New release date for 2.12

Good news, indeed and kudos to Virgin Media! Curt and James, what would you think about publishing the release during the weekend Sept. 14./15.? Or would you prefer to stick to the 17th (a Tuesday)? Torsten Am 15.08.2013 09:21, schrieb James Turner: On 14 Aug 2013, at 21:57, Curtis Olson

Re: [Flightgear-devel] Updated 707

On 14 Aug 2013, at 21:23, Stuart Buchanan wrote: > Marc Kraus (CC'd as he's not on the -devel list) has produced a (very) > significant update to the 707, a model that Innis Cunningham developed > a number of years back. > > It's available from http://gitorious.org/boeing/707 and is well worth

Re: [Flightgear-devel] 2.12 is branched

On 14 Aug 2013, at 21:57, Curtis Olson wrote: > I think the main initial hurdle here is to get the Mac & Windows releases > sorted out on Jenkins (if they aren't already). We've done the code freeze > and branch on schedule so we are mostly down to the mechanics and time of > actually buildi