20,741
edits
Howto:Optimizing FlightGear for mobile devices: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Optimizing FlightGear for mobile devices (view source)
Revision as of 06:22, 16 September 2013
, 16 September 2013http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40713.html
Philosopher (talk | contribs) m (remove heading) |
m (http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40713.html) |
||
| Line 3: | Line 3: | ||
Increasingly, people want to try running FlightGear on mobile devices, like the Apple IPhone/IPad, Android phones or Nokia Maemo devices. FlightGear isn't currently optimized for such devices, so that it would require a fair amount of customizations to make this happen, not just optimization-wise, but also related to the user-interface, i.e. lack of keyboard/mouse/yoke and screen space. | Increasingly, people want to try running FlightGear on mobile devices, like the Apple IPhone/IPad, Android phones or Nokia Maemo devices. FlightGear isn't currently optimized for such devices, so that it would require a fair amount of customizations to make this happen, not just optimization-wise, but also related to the user-interface, i.e. lack of keyboard/mouse/yoke and screen space. | ||
== Status (09/2013) == | |||
{{cquote|<nowiki>far more useful would be to get ARM | |||
working so we can run parts of the stack on Pis, Pandaboards and so on. This would be materially useful for various add-on functions, especially the canvas | |||
and fgcom. | |||
(I spend an increasing amount of my work time on OpenGL on ARM platforms, they have plenty of power to run graphics, depending on which GPU is on the SoC)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40713.html|title=<nowiki>Re: [Flightgear-devel] portability of simgear</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Sun, 08 Sep 2013 22:30:54 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}} | |||
{{cquote|<nowiki>I'm currently busy on other areas but it will be either Raspbian or a custom buildroot Linux deployment. Although, since my current buildroot uses ulibc, that would mean discovering all the places in SG+FG where we've assumed glibc. Note we can't run FG itself without major work, since these platforms only support GLES1 or GLES2, and there's many legacy areas of the renderer which would not work. | |||
(BTW I believe OSG compiles out of the box on ARM targets now, Android at least, but I didn't try it myself yet)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40738.html|title=<nowiki>Re: [Flightgear-devel] portability of simgear</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Thu, 12 Sep 2013 23:14:47 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}} | |||
<references/> | |||
== Motivation == | == Motivation == | ||