20,741
edits
FlightGear plugins: Difference between revisions
Jump to navigation
Jump to search
→Background
No edit summary |
|||
| Line 1: | Line 1: | ||
{{WIP}} | {{WIP}} | ||
{{FGCquote | |||
|1= Although the FlightGear design fairly modular it's provided as a single binary. Everyone who wants to create a new I/O module must patch the FlightGear sources and compile the FlightGear binary from scratch. This may discourage those who want to use FlightGear as a tool and extend it in some way. Moreover, it's not always possible to include all functions in a single binary. Some functions may be mutually exclusive. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/22914662/ | |||
| title = <nowiki>[Flightgear-devel] [RFC] Dynamic plug-in interface for I/O modules</nowiki> | |||
| author = <nowiki>Petr Gotthard</nowiki> | |||
| date = Jun 26th, 2009 | |||
}} | |||
}} | |||
== Background == | == Background == | ||
{{FGCquote | {{FGCquote | ||
|1= There's been talk about binary 'modules' to be loaded optionally, so that you could have optional C++ functionality, but I don't think that's feasible just yet. | |1= There's been talk about binary 'modules' to be loaded optionally, so that you could have optional C++ functionality, but I don't think that's feasible just yet. | ||