392
edits
Building FlightGear - Debian: Difference between revisions
Jump to navigation
Jump to search
m
oops
m (update to 3.2.0-RC1) |
m (oops) |
||
| Line 38: | Line 38: | ||
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-3.2</code> or <code>$HOME/FG-3.2</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. <br /> | Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-3.2</code> or <code>$HOME/FG-3.2</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. <br /> | ||
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process: | Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process: | ||
export FG_INSTALL_DIR=$HOME/FG-3.2 && mkdir $FG_INSTALL_DIR | export FG_INSTALL_DIR=$HOME/FG-3.2-rc1 && mkdir $FG_INSTALL_DIR | ||
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR | export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR | ||
Have in mind that the data is a relatively large download (GIT about 8 GiB (required disk space 18 GiB) and growing / 3. | Have in mind that the data is a relatively large download (GIT about 8 GiB (required disk space 18 GiB) and growing / 3.2 about 1.2 GB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. <br /> | ||
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. <br /> | For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. <br /> | ||