2,561
edits
m (→Proceeding) |
|||
Line 11: | Line 11: | ||
To get started creating a custom version of FlightGear, you could simply copy the whole directory tree of the FlightGear installation to a new directory and start removing everything that is obviously not needed for your particular purpose (i.e. UAV). | To get started creating a custom version of FlightGear, you could simply copy the whole directory tree of the FlightGear installation to a new directory and start removing everything that is obviously not needed for your particular purpose (i.e. UAV). | ||
Please note that this will basically create a copy of your complete FlightGear installation, so if your local installation already contains any modifications or additional scenery/aircraft packages, you might instead want to install another FlightGear version in parallel, in a different folder. | Please note that this will basically create a copy of your complete FlightGear installation (watch out for space requirements), so if your local installation already contains any modifications or additional scenery/aircraft packages, you might instead want to install another FlightGear version in parallel, in a different folder to work with a fresh, unmodified FlightGear version. | ||
'''Note:'''Advanced users may simply want to copy only their base package ($FG_ROOT) folder, instead of the whole installation tree, and start up FlightGear using their usual fgfs/fgrun binaries with a properly set --fg-root= parameter or $FG_ROOT environment variable. | '''Note:''' Advanced users may simply want to copy only their base package ($FG_ROOT) folder, instead of the whole installation tree, and start up FlightGear using their usual fgfs/fgrun binaries with a properly set --fg-root= parameter or $FG_ROOT environment variable to point FlightGear to the customized version. | ||
= Reducing Size = | = Reducing Size = |
edits