320
edits
Howto:Build and run FlightGear on Raspberry Pi 4: Difference between revisions
Jump to navigation
Jump to search
Howto:Build and run FlightGear on Raspberry Pi 4 (view source)
Revision as of 23:43, 31 March 2020
, 31 March 2020→PLIB
(→PLIB) |
(→PLIB) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 302: | Line 302: | ||
The SD card performs well for common computer tasks and running FlightGear. However, compiling large programs could wear out the SD card before it's time. This is an excellent application for a SSD drive. Especially if many compiled versions of FlightGear are planned. For that reason this Wiki will choose to compile and install FlightGear on a [[Howto:Build_and_run_FlightGear_on_Raspberry_Pi_4#Hard_Drives|SSD drive]]. | The SD card performs well for common computer tasks and running FlightGear. However, compiling large programs could wear out the SD card before it's time. This is an excellent application for a SSD drive. Especially if many compiled versions of FlightGear are planned. For that reason this Wiki will choose to compile and install FlightGear on a [[Howto:Build_and_run_FlightGear_on_Raspberry_Pi_4#Hard_Drives|SSD drive]]. | ||
This is a good time to create some needed folders on the SSD. For this Wiki the folder 'FlightGear' was created in the root of the SSD. Within this newly created folder 'FlightGear', create two more folders named 'fg-install' and 'source'. Use your favorite method to navigate and create folders, whether it be the Terminal or GUI. Furthuremore, these files can have other names as long as those other names are globally used. | This is a good time to create some needed folders on the SSD. For this Wiki the folder '''FlightGear''' was created in the root of the SSD. Within this newly created folder '''FlightGear''', create two more folders named '''fg-install''' and '''source'''. Use your favorite method to navigate and create folders, whether it be the Terminal or GUI. Furthuremore, these files can have other names as long as those other names are globally used. | ||
===PLIB=== | ===PLIB=== | ||
Compiling algorithm for [[PLIB]]. | {| class="wikitable" | ||
* Navigate the Terminal into the 'source' folder. | ! scope="col" width="80%" | Compiling algorithm for [[PLIB]]. | ||
! scope="col" width="20%" | Directory tree structure | |||
|- | |||
| | |||
* Navigate the Terminal into the '''source''' folder. | |||
* Enter the below command into the Terminal: | * Enter the below command into the Terminal: | ||
** <code>git clone git://git.code.sf.net/p/libplib/code libplib.git</code> | ** <code>git clone git://git.code.sf.net/p/libplib/code libplib.git</code> | ||
*** This will copy the needed source files into this folder 'source'. | *** This will copy the needed source files into this folder '''source'''. | ||
* Enter the below command into the Terminal: | |||
** <code>cd '''libplib.git'''</code> | |||
*** This will navigate the Terminal into the folder '''libplib.git''' that was created and populated by the <code>git</code> command. | |||
* Enter the below command into the Terminal: | * Enter the below command into the Terminal: | ||
** <code>echo "1.8.6" > version</code> | ** <code>echo "1.8.6" > version</code> | ||
***This will edit the file 'version' that is in this folder. This file can also be modified with a text editor, even via a GUI. | ***This will edit the file 'version' that is in this folder. This file can also be modified with a text editor, even via a GUI. | ||
| Line 322: | Line 326: | ||
** <code>git commit --all --message "Increase tiny version to 6."</code> | ** <code>git commit --all --message "Increase tiny version to 6."</code> | ||
*** More version patching stuff. | *** More version patching stuff. | ||
* Create a folder named 'build-plib' | * Create a folder named '''build-plib''' and have it placed in the '''source''' folder. | ||
** The <code>mkdir</code> command or a GUI method can be used to create this folder. | ** The <code>mkdir</code> command or a GUI method can be used to create this folder. | ||
** In other words; '''FlightGear/source/build-plib''' | |||
* Navigate the Terminal into the 'build-plib' folder that was just created. | * Navigate the Terminal into the '''build-plib''' folder that was just created. | ||
* Enter the below command into the Terminal: | |||
** <code>cmake -D CMAKE_INSTALL_PREFIX:PATH='''fg-install''' '''libplib.git'''</code> | |||
*** The two folders '''fg-install''' and '''libplib.git''' need to be replaced with the relative or absolute address of these folders. Use your favorite method. | |||
*** The absolute address can easily be copied and pasted with the above [[Howto:Build_and_run_FlightGear_on_Raspberry_Pi_4#Copy_Path(s)|Copy Path(s)]] method. This could be a large string, however the Terminal doesn't mind. | |||
** This will setup the build. | |||
* Enter the below command into the Terminal: | |||
** <code>make -j3</code> | |||
*** This will perform the compiling. | |||
*** The <code>-j3</code> argument will allow three of the Pi's cores to participate in the compiling process. | |||
* Enter the below command into the Terminal: | |||
** <code>make install</code> | |||
** PLIB will be installed into the '''source''' folder. | |||
{{not done}} | |||
| {{not done}} | |||
|} | |||
==Performance settings == | ==Performance settings == | ||