20,741
edits
FlightGear and OpenGL Core Profile: Difference between revisions
Jump to navigation
Jump to search
m
→Approach
m (→Approach) |
|||
| Line 47: | Line 47: | ||
Whenever FlightGear sources contain such or similar code, it is pretty safe to assume that we will need to port/exclude such modules from compilation to ensure that no legacy OpenGL code is executed at runtime. | Whenever FlightGear sources contain such or similar code, it is pretty safe to assume that we will need to port/exclude such modules from compilation to ensure that no legacy OpenGL code is executed at runtime. | ||
<syntaxhighlight> | |||
Instrumentation/HUD/HUD_runway.cxx | |||
Instrumentation/HUD/HUD_tbi.cxx | |||
Instrumentation/HUD/HUD.hxx | |||
Instrumentation/HUD/HUD_instrument.cxx | |||
Instrumentation/HUD/HUD_ladder.cxx | |||
Instrumentation/HUD/HUD_dial.cxx | |||
Instrumentation/HUD/HUD_tape.cxx | |||
Cockpit/render_area_2d.cxx | |||
Cockpit/panel.cxx | |||
GUI/WaypointList.cxx | |||
GUI/CanvasWidget.cxx | |||
GUI/MapWidget.cxx | |||
</syntaxhighlight> | |||
This means, we'll need to review/disable the compilation of the following folders in $FG_SRC and patch up all hard-coded references to these systems: | |||
* Instrumentation/HUD | |||
* Cockpit | |||
* GUI | |||
== Example: disabling PUI == | == Example: disabling PUI == | ||