50
edits
Fedora Packages and Compiling: Difference between revisions
Jump to navigation
Jump to search
→Current release version 2024.1
m (/* move fgdata to its default location.) |
|||
| Line 63: | Line 63: | ||
This example gives the simple case of a single private version in your HOME directory. | This example gives the simple case of a single private version in your HOME directory. | ||
mkdir $HOME/fg2024.1 | mkdir $HOME/fg2024.1 | ||
Two methods exist to get the required source code. Tar archives or the FlightGear git repository. | Two methods exist to get the required source code. Tar archives or the FlightGear git repository. | ||
| Line 87: | Line 86: | ||
{{simgear clone | opt = --single-branch --branch release/2024.1 | post = simgear}} | {{simgear clone | opt = --single-branch --branch release/2024.1 | post = simgear}} | ||
{{flightgear clone | opt = --single-branch --branch release/2024.1 | post = flightgear}} | {{flightgear clone | opt = --single-branch --branch release/2024.1 | post = flightgear}} | ||
{{fgdata clone | opt = --single-branch --branch release/2024.1 | post = fgdata}} | |||
{{fgdata clone | opt = --single-branch --branch release/2024.1 | post = | |||
==== Building 2024.1 ==== | ==== Building 2024.1 ==== | ||
| Line 106: | Line 104: | ||
make -j$(nproc) | make -j$(nproc) | ||
make install | make install | ||
FlightGear should now be installed in the local install directory. | FlightGear should now be installed in the specified local install directory. Set your path to find the new executables. | ||
export PATH=$HOME/fg2024.1/install/bin:$PATH | export PATH=$HOME/fg2024.1/install/bin:$PATH | ||
The build procedure looks for the fgdata files in a few different places controlled by cmake. | |||
One can specify a specific location for fgdata when configuring flightgear: | |||
cmake ../flightgear -DFG_DATA_DIR=$HOME/my-fgdata ... | |||
If no such fgdata directory is specified to cmake, it looks for a directory called fgdata at the same level as the specified flightgear source directory. This is the method used above in the example build. The fgdata directory is found at ../fgdata: | |||
cmake ../flightgear ... | |||
Finally, if not otherwise found, cmake sets the fgdata directory to be a sub directory of the place where flightgear and simgear are to be installed. In an example where fgdata was not installed at ../fgdata as above, the fgdata directory will be found in $HOME/fg2024.1/install/lib/fgdata: | |||
cmake ../flightgear -DCMAKE_INSTALL_PREFIX=$HOME/fg2024.1/install ... | |||
In any of the cases, messages output by cmake as it runs will tell you what directory was selected for the flightgear data directory. Development is under consideration for future versions to allow portions of the fgdata data to be dynamically downloaded from the internet. | |||
===Next development version 2024.2=== | ===Next development version 2024.2=== | ||