Howto:Optimizing FlightGear for mobile devices: Difference between revisions

Howto:Optimizing FlightGear for mobile devices (view source)

1,025 bytes added , 28 July 2012

m

20,741

edits

@@ Line 118: / Line 118: @@
 There are many other subsystems which are started by default and which cannot be currently disabled, so more CPU/RAM resources can be saved by editing [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1043 $FG_SRC/Main/fg_init.cxx] and by making more subsystems optional there, using a property to decide if the subsystem shall be started or not.
+Some possible candidates include:
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1052 the sounds system]
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1081 the performance monitor]
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1133 the autopilot/route manager systems]
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1178 the ATC system]
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1196 the traffic manager]
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1225 the replay system]
+* [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1230 the voice system]
+While disabling these systems can be fairly easily accomplished using ifdefs, care must be taken that FlightGear still builds properly and that no other systems are trying to access disabled subsystems, so this will involve repeated edit/build/debugging sessions using gdb.
 == OpenGL vs. OpenGL ES ==