20,741
edits
| Line 156: | Line 156: | ||
Also, you can get a fair amount of information out of the FG sources by running them through doxygen, too. | Also, you can get a fair amount of information out of the FG sources by running them through doxygen, too. | ||
== | == Plain C ? == | ||
If you'd just like to get started quickly, there are also certain FG components that are strictly (largely) pure C, the Nasal interpreter is just one example (Nasal is FlightGear's built in scripting language): http://wiki.flightgear.org/Nasal_scripting_language | If your C++ is rusty and you'd just like to get started quickly, there are also certain FG components that are strictly (largely) pure C, the Nasal interpreter is just one example (Nasal is FlightGear's built in scripting language): http://wiki.flightgear.org/Nasal_scripting_language | ||
The Nasal interpreter is part of the SimGear project, and can be found in $SG_SRC/nasal | The Nasal interpreter is part of the SimGear project, and can be found in $SG_SRC/nasal: http://gitorious.org/fg/simgear/trees/next/simgear/nasal | ||
Adding new extension functions to the built-in Nasal interpreter is documented here: [[Howto: Extend Nasal]]. | Adding new extension functions to the built-in Nasal interpreter is documented here: [[Howto: Extend Nasal]]. | ||
There's also a separate wiki article providing a list of issues related to the Nasal interpreter itself: [[Improving Nasal]]. | |||
= Getting started = | = Getting started = | ||