FlightGear Newsletter May 2015: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter May 2015 (view source)

Revision as of 15:00, 2 June 2015

850 bytes removed ,  2 June 2015
More prep (WIP section)
m (fix typo)
(More prep (WIP section))
Line 38: Line 38:


=== Automated checklist execution ===
=== Automated checklist execution ===
{{FGCquote
User {{usr|sanhozay}}, as part of the development of the [[Lockheed Constellation]], has developed a new script that automatically exceutes checklist bindings in sequence.<ref>
  |As part of the development of the Lockheed 1049h Constellation, I created a comprehensive set of checklists based on the crew operating manual with other items added sufficient to take the aircraft through all stages of flight. Rather than hand-code an autostart script I wrote a more generic script to run checklist bindings in sequence. This script is now available in FGDATA and can be used on other aircraft:<br/>
{{cite web
<br/>
|url   = http://forum.flightgear.org/viewtopic.php?p=241203#p241203
[[Aircraft_Checklists#Automated_checklist_execution|Wiki: Automated Checklist Execution]]<br/>
|title = Automated Checklist Execution
<br/>
|author = sanhozay
If you are thinking about writing an autostart menu, you might want to consider using this script and driving the autostart from the checklists. It's not restricted to autostart, you can essentially run any sequence of checklists from any piece of Nasal code.<br/>
|date   = May 1st, 2015
<br/>
You can see the script in action in the latest [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Lockheed1049h/ Lockheed 1049h]. Note that you need a recent copy of [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/ FGDATA] for this to work. The autostart in this case is intelligent enough to run different checklist sequences depending on whether you are starting on a runway, at the terminal or in the air and also uses automated checklist execution to run an "After Landing" checklist from a keyboard shortcut during that busy time of rollout and taxi.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=241203&sid=4bad6d92dab1d411ea46e6efb1b8850c#p241203
    |title=<nowiki>Automated Checklist Execution</nowiki>
    |author=<nowiki>sanhozay</nowiki>
    |date=<nowiki>Fri May 01</nowiki>
  }}
}}
}}
</ref>  The script enables aircraft developers to execute checklists from any Nasal script.
The script can be seen in action on the latest Lockheed Constellation from [[FGAddon]], although you will need the latest copy of FGData (or a copy of [http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Generic/autochecklist.nas autochecklist.nas]).
You can find out more at [[Aircraft Checklists#Automated checklist execution]].
<references/>


=== Submodel enhancements ===
=== Submodel enhancements ===
Line 79: Line 79:


=== Cross-compiling FlightGear ===
=== Cross-compiling FlightGear ===
{{WIP}}
Users hamzaalloush and saiarcot895 have been making lots of progress using [http://mxe.cc/ MXE] and [http://www.mingw.org/ MinGW] to build Windows binaries on Linux.  The goal is to provide FlightGear/osgEarth binaries for Windows end-users via cross-compiling on Linux, so that end-users no longer need to be able to build FlightGear from source, but can just download pre-compiled binaries for different FlightGear versions.  As of May 2015, OpenSceneGraph and osgEarth can be cross-compiled and run most of their respective examples:


{{FGCquote
{{#ev:youtube|ddYyH5CYhAo|400}}
  |During the last two weeks, hamzaalloush and saiarcot895 have been making lots of progress using mxe/mingw to build Windows binaries on Linux. The mid-term goal here is to provide FG/osgEarth binaries for Windows end-users via cross-compiling on Linux, so that end-users no longer need to be able to patch &amp; build FG from source, but can just download pre-compiled binaries for 3.4 (and probably 3.6 in a few months time).
{{#ev:youtube|mTHhHMlTSAo|400}}
 
{{#ev:youtube|sfWVo5u_7lw|400}}
We're looking for people with access to Linux/Windows to help with testing/developing cross-compiled binaries for Windows on Linux using the mxe toolchain.


If anybody wants to get involved, please leave your system specs (OS, distro) here - so that we can grow a list of people familiar with both, Linux and Windows (alternatively, emulation/virtualization via VirtualBox/Qemu etc) - for now, we are primarily looking for people familiar with building FG from source, and ideally also familiar with using git.  
Currently, people primarily familiar with building FlightGear from source and ideally also using git are invited to join to efforts.  Having access to Linux and/or Windows to help with testing or developing these cross-compiled binaries is also very helpful.  People familiar with CMake, the GNU build system, or GCC (GNU Compiler Collection) internals are also invited to help.  In addition To show your interest, please leave your system specs (OS, distribution) on the [http://forum.flightgear.org/viewtopic.php?p=244898#p244898 forum thread] so a list can be made of people familiar with both Linux and Windows (alternatively, emulation/virtualization via VirtualBox/Qemu, etc.), although for now we are primarily looking for people familiar with building FG from source, and ideally also familiar with using git.  


Note that most testing/development is currently taking place on Ubuntu 14.04 - so people on a different distro should be prepared to do some integration/porting work (e.g. matching packages etc).
Note that most testing/development is currently taking place on Ubuntu 14.04 - so people on a different distro should be prepared to do some integration/porting work (e.g. matching packages etc).
Currently, we're able to cross-compile OpenSceneGraph and osgEarth on Linux for Windows and run most OSG/OsgEarth examples:
{{#ev:youtube|ddYyH5CYhAo|400|center}}
{{#ev:youtube|mTHhHMlTSAo|400|center}}
{{#ev:youtube|sfWVo5u_7lw|400|center}}


The next steps ahead are getting osgEarth.mk to compile/link via mxe, and creating corresponding simgear.mk/flightgear.mk for mxe, at which point we will investigate porting poweroftwo's autobuilder to use mxe for building a patched version of sg/fg including osgEarth support.
The next steps ahead are getting osgEarth.mk to compile/link via mxe, and creating corresponding simgear.mk/flightgear.mk for mxe, at which point we will investigate porting poweroftwo's autobuilder to use mxe for building a patched version of sg/fg including osgEarth support.


People familiar with cmake/autotools or gcc internals are obviously also invited to get involved  :D 
For details and updates, please refer to [[Building FlightGear - Cross Compiling]].


For details and updates, please refer to: [[Building_FlightGear_-_Cross_Compiling]]
You can find out more on the [http://forum.flightgear.org/viewtopic.php?p=244898#p244898 forum thread]
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=244898#p244898
    |title=<nowiki>Dual Linux/Windows users:Cross-compiling FG/osgEarth for Win</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Sun May 31</nowiki>
  }}
}}


== In the Hangar ==
== In the Hangar ==
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/85331"

Navigation menu