50
edits
m (update section headers) |
(More heading cleanup) |
||
| Line 88: | Line 88: | ||
git clone --single-branch --branch release/2024.1 git://git.code.sf.net/p/flightgear/fgdata fgdata | git clone --single-branch --branch release/2024.1 git://git.code.sf.net/p/flightgear/fgdata fgdata | ||
==== Building 2024.1 ==== | |||
Once the code is loaded we can build. The general technique is to make a separate empty build directory, use cmake to configure and then compile and link. This avoids cluttering up the source directories with build files. Also, you can have several different configurations with the same source: fgbuild-release, fgbuild-debug, fgbuild-test, etc. | Once the code is loaded we can build. The general technique is to make a separate empty build directory, use cmake to configure and then compile and link. This avoids cluttering up the source directories with build files. Also, you can have several different configurations with the same source: fgbuild-release, fgbuild-debug, fgbuild-test, etc. | ||
mkdir fgbuild | mkdir fgbuild | ||
edits