Re: [Flightgear-devel] TerraSync libSVN replacement testing
On 21 Jul 2013, at 13:45, Alan Teeder ajtee...@v-twin.org.uk wrote: What is the status of this on Windows 64 bit? Up until now I have kept with 32 bit builds on Windows due to the lack of a 64 bit version of libSvn. The replacement code is disabled by default on next, and 2.12 will certainly not use it. My plan is to enable it (and require it) for 3.0, but I won't make that change until after 2.12 is released, since I'm aware of some intermitted issues with the code, where it gets stuck 'not doing anything'. This is happening for some people erratically, but is annoying, and obviously precludes enabling the code by default! Gijs also reported a crash on Windows - help tracking that down would be most welcome. 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] Download_and_compile.sh
On 20 Jul 2013, at 15:06, Pat pat.callah...@gmail.com wrote: Eventually I'd like to have a maintainable version on each branch. What we have in fgmeta master and fgmeta 2.10.0 is script version 1.9.4 The one on 2.8.0 is even older, 1.31. None of these work, mostly because of the osg svn url change and maybe other things. Someone would have to test to find out. Script version 1.9.10 which is currently on next does work as is for next and 2.8.0. You could merge that version back to master and the download_and_compile.sh instructions on the wiki will work again. I can backport the -B and -V options from the new script to a 1.9.11 based on 2.10.0. This minor change would mean the existing script could support next/master, 2.12.0, 2.10.0, 2.8.0 and maybe even 2.6.0. Let me know if you want me to do that. To be honest I'm not sure. In general, we don't touch the branches for prior releases (although of course we could). Of course the versions on master and next need to be kept up-to-date. Personally I don't see any value in encouraging people to run older versions of the sim; if people experience problems with newer versions, I'd far rather they reported that than kept using 2.6 or 2.8. There may be valid reasons to stick with a particular version for a dedicated project or similar, but for the kind of users download-and-compile is aimed at, supporting the current and previous stable releases seems sufficient to me. (Possibly as a Mac user my opinion on this is a little distorted!) However, download_and_compile is a little special, in that it supports multiple versions in a single file, so if you can create a compatible version with some small tweaks, then go for it, I guess. I would expect, ideally, that the version on master would build the current official release by default, and the versions on release/2.12.0 and next would build that explicit release, and next, by default respectively. Hopefully this is a one line change in the script when branching fgmeta? 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] Download_and_compile.sh
James and Francesco, Proposal: The version of the script on the official fgmeta next, master and the upcoming release branch and should be maintained and should work. The same script version can be on each of these branches. Currently master does not work. next thinks stable is 2.8.0. Note that this message is not a request to merge, just a proposal for how to operate going forward. Right now in the official fgmeta, we have: fgmeta script script the script branch version status builds: -- --- -- -- next: 1.9.10 (working) next and 2.8.0 master 1.9.4 (not working) 2.12.0 1.9.10 (working) next and 2.8.0 2.10.0 1.9.4 (not working) in the fgmeta team clone we have: next: 1.9.tbd working but next, master, 2.12.0, not fully 2.10.0 2.8.0 tested OSG: 3.0.1 and any other named branch of OSG master 1.9.11 not releasednext and 2.8.0 untested minor changes Suggestion: backport the changes in 1.9.tbd that allows builds of next,master, 2.12.0, 2.10.0 etc to script version 1.9.11, test it and release it on Francesco's approval. or we could just fix 1.9.10 Thoughts? -Pat PS. You may be asking how big a change would it be to allow the script to build basically any branch, tag or commit# Not too bad: -- 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
