Re: [Flightgear-devel] FGRun improvements
On 16 Jul 2013, at 21:46, Gijs de Rooy gijsr...@hotmail.com wrote: Anyone? Please... I'll apply it. James -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] 2.12 is branched
Hi, I've just created the release branches for FG, SG data (at Torsten's request, since he's on holiday in the wild, Internet-less north of Sweden). Hopefully I didn't screw anything up :) This means 'next' is open for unstable work, and that bug-fixes should be applied to both next release branch and next as appropriate, preferably after a code-review cycle. I've set the version files on 'next' to be 2.99, on the assumption the next release will be 3.0 as discussed. Regards, James -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Changelog 2.12
On Mon, Jul 15, 2013 at 9:22 PM, Gijs de Rooy wrote: Hi Stuart, thanks for the improvements! Checking the diff I do wonder if you removed the Microsoft SideWinder Precision Racing Wheel (rudder) pedals line on purpose? Vivian added this one in March... https://gitorious.org/fg/fgdata/commit/9dcb78c2248 Good spot. That was a mistake. Now corrected. -Stuart -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Re: Bug#716834: libfltk1.3-dev: --ldflags should contain -ldl
The patches as described allowed me to build both fgadmin and fgrun on Ubuntu 13.10 and on Ubuntu 12.10 Can someone tell me what the right way to get these changes committed to next? Do the maintainers respond best to 1. a git merge request, 2. a git merge request and an email on fg-devel 3 an email on fg-devel with the patches attached What's preferred? Who do we ask for commits to fgfs Who for fgrun? gijs? Is now the right time? ( builds on Ubuntu 13.04 are broken without this fix) -Pat This is one way to do it: https://gitorious.org/~hof/fg/hof-flightgear/commit/d379698b72d0191d98e5c2f14cf049415b867c0b https://gitorious.org/%7Ehof/fg/hof-flightgear/commit/d379698b72d0191d98e5c2f14cf049415b867c0b Patch checks if the system supports libdl and if so, adds it to the library list. Cheers, Hof snip -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Re: Bug#716834: libfltk1.3-dev: --ldflags should contain -ldl
Patches are git merge-requested on flightgear (#1572) and fgrun (#3). Hof On 7/17/2013 9:22 PM, Pat wrote: The patches as described allowed me to build both fgadmin and fgrun on Ubuntu 13.10 and on Ubuntu 12.10 Can someone tell me what the right way to get these changes committed to next? Do the maintainers respond best to 1. a git merge request, 2. a git merge request and an email on fg-devel 3 an email on fg-devel with the patches attached What's preferred? Who do we ask for commits to fgfs Who for fgrun?gijs? Is now the right time? ( builds on Ubuntu 13.04 are broken without this fix) -Pat This is one way to do it: https://gitorious.org/~hof/fg/hof-flightgear/commit/d379698b72d0191d98e5c2f14cf049415b867c0b https://gitorious.org/%7Ehof/fg/hof-flightgear/commit/d379698b72d0191d98e5c2f14cf049415b867c0b Patch checks if the system supports libdl and if so, adds it to the library list. Cheers, Hof snip -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
