20,741
edits
Howto:Start core development: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 78: | Line 78: | ||
* don't get frustrated :-) | * don't get frustrated :-) | ||
* enjoy! | * enjoy! | ||
= Project architecture = | |||
FlightGear itself consists of a number of different projects and dependencies (libraries), please refer to gitorious for details. Most of FlightGear's supporting code is increasingly getting moved to the "SimGear" project. | |||
Basically, FlightGear depends on SimGear, while SimGear depends on some 3rd party libraries such as OpenSceneGraph, plib, OpenAL and others. | |||
Once you have satisfied all dependencies and built them in the right order, you can start FlightGear. | |||
Note however that FlightGear also has a run time dependency: its so called "base package", i.e. the data package that contains all resources such as scenery, GUI files, aircraft, sounds and so on. We commonly refer to this as "$FG_ROOT". | |||
The FG source tree is commonly referred to as $FG_SRC, while the SimGear source tree is often referred to as $SG_SRC. | |||
= The source code = | = The source code = | ||
| Line 138: | Line 149: | ||
You are obviously invited to start your own wiki articles, in order to document your projects or help improving existing documentation. Also, some core developers actually use the wiki to post their own development roadmaps. For example, see: [[Plan-zakalawe]] or [[Project Rembrandt]]. | You are obviously invited to start your own wiki articles, in order to document your projects or help improving existing documentation. Also, some core developers actually use the wiki to post their own development roadmaps. For example, see: [[Plan-zakalawe]] or [[Project Rembrandt]]. | ||
== FlightGear == | == FlightGear == | ||