andermatt64 / ACARS-AppImage-Kit

AppImage build system for SDR++, JAERO, SDRReceiver, acarsdec (RTLSDR), dumphfdl (Airspy HF+ via SoapySDR), dumpvdl2 (RTLSDR). Packages are tested and confirmed to work on Steam Deck

ACARS AppImage Kit

AppImage build kit for ACARS-related toolset.

How do I use this?

To start the build, run

./build-acars-kit.sh

After the script successfully completes, the export/ directory will be populated with AppImages.

What AppImages are built?

The following AppImages are then built with the above tools and libraries:

• acarsdec-x86_64.AppImage (RTL-SDR support only)
• dumphfdl-x86_64.AppImage (RTL-SDR + SoapySDR w/ Airspy HF)
• dumpvdl2-x86_64.AppImage (RTL-SDR + SoapySDR)
• JAERO-x86_64.AppImage (AeroAMBE + ZeroMQ)
• SDR++-x86_64.AppImage (RTL-SDR + SoapySDR + Airspy/Airspy HF + HackRF + Audio Sink)
• SDRReceiver-x86_64.AppImage (RTL-SDR)

What libaries/tools are you building with?

We pull and compile the latest version of the following libraries/tools:

• SoapySDR
• libacars
• acarsdec
• dumpvdl2
• airspyhf
• SoapyAirspyHF
• dumphfdl
• qmqtt
• libcorrect
• libaeroambe
• JFFT
• JAERO
• SDRReceiver
• airspyone_host
• SDRPlusPlus

What platform are these AppImages targeting/tested for?

The AppImages are built in a x86_64 Debian Bullseye container with glibc 2.31. In theory, any Linux distro with glibc 2.31 and above should be able to run the AppImages.

The primary target platform for these AppImages is the SteamDeck. However, we have tested and confirmed that it also works on the following configurations:

• Debian Bullseye (x86_64)
• Fedora 36 (x86_64)
• SteamDeck SteamOS

Why do you use a forked SDRPlusPlus?

SDRPlusPlus is not AppImage friendly by default. It uses a config.json that defines the modules and resources directory as a hardcoded value. We had to modify the logic to dynamically find the installation prefix. The bulk of the changes are in core/src/core.cpp for those interested.