20,741
edits
Talk:Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions
Jump to navigation
Jump to search
Talk:Scripted Compilation on Linux Debian/Ubuntu (view source)
Revision as of 17:25, 20 September 2013
, 20 September 2013→Experimental TerraSync / libsvn support: new section
(→git: Use the git command instead of editing the .git/config file) |
(→Experimental TerraSync / libsvn support: new section) |
||
| Line 287: | Line 287: | ||
:: The "test run" idea is not really new and very popular, and IIRC it was once a part of the old autotools system - meanwhile, a number of users have suggested some form of "testing framework" (via some custom/restricted startup mode built into FG), see [[FlightGear Headless]] and [[FlightGear Benchmark]] for a summary of the various discussions here. Basically, we are half-way there already, we really only need to make the GUI window optional and some additional subsystems that are currently enabled by default. Some core developers have been working on better regression testing support by making subsystems increasinly optional, see [[FlightGear Run Levels]]. Thus, a scripted test would already be possible to a certain degree, but may require additional customizations for certain scenarios. However, we shouldn't really be using any bash-magic here, because scripted test runs of FG would ideally be as platform-independent as FG itself, so that they could be run via CMake/CTest and/or the build server.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 00:17, 9 August 2013 (UTC) | :: The "test run" idea is not really new and very popular, and IIRC it was once a part of the old autotools system - meanwhile, a number of users have suggested some form of "testing framework" (via some custom/restricted startup mode built into FG), see [[FlightGear Headless]] and [[FlightGear Benchmark]] for a summary of the various discussions here. Basically, we are half-way there already, we really only need to make the GUI window optional and some additional subsystems that are currently enabled by default. Some core developers have been working on better regression testing support by making subsystems increasinly optional, see [[FlightGear Run Levels]]. Thus, a scripted test would already be possible to a certain degree, but may require additional customizations for certain scenarios. However, we shouldn't really be using any bash-magic here, because scripted test runs of FG would ideally be as platform-independent as FG itself, so that they could be run via CMake/CTest and/or the build server.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 00:17, 9 August 2013 (UTC) | ||
<references/> | |||
== Experimental TerraSync / libsvn support == | |||
SimGear 2.11+ now has experimental support for a libsvn replacement, people building from source are encouraged to help with testing and debugging this new feature: | |||
{{cquote|<nowiki>First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40191.html|title=TerraSync libSVN replacement testing|author=James Turner|date=Tue, 11 Jun 2013 08:58:20 -0700}}</ref>|James Turner}} | |||
{{cquote|<nowiki>So, as I've previously asked before, I really need people running from 'next' | |||
to try with -DSG_SVN_CLIENT=1 when configuring SimGear, move their existing | |||
TerraSync dir out the way, and test, test, test. I'm sure the new code isn't | |||
100% trouble free (in particular I think there is still the occasional time | |||
when it gets stuck not doing any more downloads until FG is restarted), but I | |||
really don't want to move forwards with the code until I have a bit more | |||
assurance it's not going to make everyone's setup crash 80% of the time, which | |||
is what some people have reported. | |||
Note this applies even if you 'don't use' terrasync since the SVN sync engine | |||
is going to be used for other pieces of data as soon as it's stable. (I will be | |||
adding a new preference to globally control whether FG works in online/offline | |||
mode, of course)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40775.html|title=<nowiki>[Flightgear-devel] Built-in Svn client code crashing</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Fri, 20 Sep 2013 09:54:38 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}} | |||
<references/> | <references/> | ||