20,741
edits
Python in FlightGear: Difference between revisions
Jump to navigation
Jump to search
→Background
| Line 16: | Line 16: | ||
| title = <nowiki>FGPython an propose for Python as an nasal alternative</nowiki> | | title = <nowiki>FGPython an propose for Python as an nasal alternative</nowiki> | ||
| author = <nowiki>www2</nowiki> | | author = <nowiki>www2</nowiki> | ||
| date = Dec 28th, 2015 | |||
| added = Dec 28th, 2015 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I think the first hurdle towards python integration would be an interface to the property system. I have another project (a UAV autopilot system) that is built using the FlightGear properties, and I have a longer term interest in python integration there too. For the FlightGear project specifically, it would be important to proceed in a way that doesn't create headaches for the build system ... i.e. we need to be able to build on Windows, Mac, and Linux. Typically we are adverse to adding new build dependencies. We are less adverse to adding 'optional' build dependencies. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=270326#p270326 | |||
| title = <nowiki>Re: FGPython an propose for Python as an nasal alternative</nowiki> | |||
| author = <nowiki>curt</nowiki> | |||
| date = Dec 28th, 2015 | | date = Dec 28th, 2015 | ||
| added = Dec 28th, 2015 | | added = Dec 28th, 2015 | ||