Difference between revisions of "Howto:Build and run FlightGear on Raspberry Pi 4"

From FlightGear wiki
Jump to navigation Jump to search
Line 59: Line 59:
 
gdb: bt
 
gdb: bt
 
</syntaxhighlight>
 
</syntaxhighlight>
 
==osgviewer==
 
Using the command line osgviewer to display models. These instructions are for FlightGear and OSG built with download_and_compile.sh.
 
 
<syntaxhighlight>
 
cd /flightgear/dnc-managed/install/openscenegraph/bin
 
 
export LD_LIBRARY_PATH=../openscenegraph/lib:$LD_LIBRARY_PATH
 
 
./osgviewer "path to your model file"
 
</syntaxhighlight>
 
 
Type <code>h</code> for the help menu.
 
  
  

Revision as of 02:59, 6 January 2021


It is now possible to run FlightGear on a Raspberry Pi, starting with the model Pi 4. The objective of Howto:Build and run FlightGear on Raspberry Pi 4 is to introduce Pi users to FlightGear and possibly FlightGear users to the Raspberry Pi family. One of the main objectives of the Raspberry Pi is education. Hopefully this marriage will introduce some young programmers to FlightGear. Although this will mainly deal with the Pi 4, other models may find applications in the area of flight panels and instruments.

Gallery

Update Raspbian

Use the below commands to update your Raspberry Pi:

sudo apt-get update
sudo apt-get full-upgrade

Do not use the below update command unless you know how and why to use it. This command will install experimental software that has a good chance of breaking your operating system. It is like flying into a thunder storm cloud.

sudo rpi-update          (DO NOT USE)

Backtrace using gdb: and Download_and_compile.sh

Tracking down a crash with double free corruption (fasttop)

Set environment variable:

set environment MALLOC_CHECK_ 2

Next run FlightGear with debug:

./run_fgfs_debug.sh --launcher

Use the below gdb commands handle SIGPIPE nostop and handle SIG32 nostop to skip innocent events:

gdb: handle SIGPIPE nostop
gdb: handle SIG32 nostop

Use r within gdb to run FlightGear:

gdb: r

After the crash use the gdb command bt to print the backtrace:

gdb: bt