Skip to content

Linux Build

harrypm edited this page Aug 18, 2026 · 2 revisions

Linux Installation

Previous Page Installation | Home

Next Page MacOS Build | Windows Build

analyse

TBC Tools (ld-analyse) — the GUI analysis & export hub of the tbc-tools suite.

These instructions cover installing and building tbc-tools only — the post-decode TBC processing toolchain. It consumes .tbc files produced by the RF decode projects; the decoders themselves are separate repositories and are not covered here.

Downloads

Self-contained AppImage binaries are the recommended way to run tbc-tools in production:

The official Linux AppImage is built for x86_64 (built on an oraclelinux:8 baseline with Nix, so it runs on any glibc ≥ 2.28). It bundles the full tool suite plus FFmpeg/FFprobe and the self-contained tbc-video-export, so no system dependencies are required beyond a working glibc.

Note

AppImage files need read/write and self-execution permissions.

To give the AppImage permissions, open a terminal in the directory and use:

chmod +x tbc-tools.AppImage

If the file is not named the above, just rename it before running the command.

Binary Usage

Run the AppImage like any normal GUI app to open ld-analyse:

./tbc-tools.AppImage

The ld-xxxx CLI tools and tbc-video-export are bundled in the same AppImage and can be called directly from the extracted AppDir, or run the GUI and use the Export page for end-to-end chroma-decode + encode via FFmpeg.

Manual Building

This is the workflow to manually build the tbc-tools suite from source.

As of 2026 this is aimed at users who wish to develop and tinker with tbc-tools rather than run it in a fixed production way — production use should be based around the binary releases above.

Recommended: Nix (reproducible)

tbc-tools ships a Nix flake that pins all dependencies (Qt6, FFmpeg, FFTW, SQLite, OpenGL). See INSTALL.md and BUILD.md in the repository for full details.

Install into your user profile:

nix profile install .#

Build without installing (output under ./result):

nix build .#
./result/bin/ld-analyse

Enter the dev shell and build manually:

nix develop
cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
ninja -C build

Or one-off without entering the shell:

nix develop -c cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
nix develop -c ninja -C build

Note

Nix requires flakes enabled — set experimental-features = nix-command flakes in your Nix config. The flake sets -DEZPWD_DIR, -DAPP_BRANCH, and -DAPP_COMMIT automatically for nix build/nix profile install; inside nix develop the EZPWD_DIR env var is exported so manual cmake/ninja picks it up.

Native distro packages (manual build)

Before building, ensure submodules are present (required for ezpwd):

git clone https://github.com/harrypm/tbc-tools.git
cd tbc-tools
git submodule update --init --recursive

Install dependencies for your distro family. Package names can vary slightly by distro release; if one package name differs, install the equivalent Qt6/FFTW/SQLite/FFmpeg development package for your release.

Debian/Ubuntu (including Linux Mint)

sudo apt update
sudo apt install -y build-essential cmake ninja-build pkg-config qt6-base-dev qt6-tools-dev qt6-tools-dev-tools libqt6svg6-dev libfftw3-dev libsqlite3-dev ffmpeg libgl1-mesa-dev python3 python3-numpy

Fedora

sudo dnf install -y gcc-c++ cmake ninja-build pkgconf-pkg-config qt6-qtbase-devel qt6-qtsvg-devel fftw-devel sqlite-devel ffmpeg ffmpeg-devel mesa-libGL-devel python3 python3-numpy

Arch Linux / EndeavourOS / Manjaro

sudo pacman -S --needed base-devel cmake ninja pkgconf qt6-base qt6-svg fftw sqlite ffmpeg mesa python python-numpy

openSUSE Tumbleweed/Leap

sudo zypper install -y gcc-c++ cmake ninja pkgconf-pkg-config qt6-base-devel libqt6-qtsvg-devel fftw3-devel sqlite3-devel ffmpeg Mesa-libGL-devel python3 python3-numpy

Build and install

cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build build -j"$(nproc)"
sudo cmake --install build

If you do not want to install system-wide, run the tools directly from build/bin/.

Note

Out-of-source builds are enforced by CMakeLists.txt — always build in build/ (or another separate directory), never in the source tree.

Local CI parity checks

To keep local validation aligned with GitHub Actions, run the same guardrails and build/test flow locally before pushing:

bash ci/run_local_ci_parity.sh

Useful scoped modes:

bash ci/run_local_ci_parity.sh --guardrails-only
bash ci/run_local_ci_parity.sh --build-test-only

How to Update

To update your local repository run git pull inside the tbc-tools directory, then repeat the build steps above. There is usually no need to delete existing files — re-running cmake --build build rebuilds only what changed. If a build fails after an update, clean and reconfigure:

rm -rf build
cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build build -j"$(nproc)"

For Nix profile installs, re-run nix profile install .# after git pull to upgrade in place.

For the binary AppImage release, there is no automatic update — check the releases page from time to time and replace the old AppImage.

Page End

Previous Page Installation | Home

Clone this wiki locally