18
edits
(removed references to stuff that is not going to happen.) |
Flyingsolo (talk | contribs) (adding FGRUN in Optimus d&c section?) |
||
| Line 139: | Line 139: | ||
:: 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) | ||
* Optimus section to include FGRUN? | |||
[[User:Flyingsolo|Flyingsolo]] ([[User talk:Flyingsolo|talk]]) 22:50, 18 March 2015 (EDT) | |||
:: why not add FGRUN to the Optimus section after FGFS: | |||
:: "Now you can run FG with ./run_fgfs_optirun.sh | |||
:: similarly, if you use the FGRUN launcher and want to enable optimus technology, navigate to the install directory where run_fgrun.sh is located, and execute: | |||
<pre> | |||
sed 's|\./fgrun|optirun ./fgrun|' run_fgrun.sh > run_fgrun_optirun.sh && chmod +x run_fgrun_optirun.sh | |||
</pre> | |||
:: Now you can run FGRUN with ./run_fgrun_optirun.sh" | |||
<references/> | <references/> | ||
edits