hyperion.ng/doc/development/CompileHowto.md

10 KiB

With Docker

If you are using Docker, you can compile Hyperion inside a docker container. This keeps your system clean and with a simple script it's easy to use. Supported is also cross compiling for Raspberry Pi (Debian Buster or higher). To compile Hyperion just execute one of the following commands.

The compiled binaries and packages will be available at the deploy folder next to the script.

[!NOTE] Call the script with ./docker-compile.sh --help for more options.

Cross compilation on amd64 (aka x86_64), sample commands

Debian

amd64 (Bookworm):

wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh --name bookworm

arm64 or Raspberry Pi 5 (Bookworm)

wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh --architecture arm64 --name bookworm

Raspberry Pi 2/3/4 (Bookworm)

wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh --architecture arm/v7 --name bookworm

Raspberry Pi v1 & ZERO (Bookworm)

wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh --architecture arm/v6 --name bookworm

Ubuntu

amd64 (Jammy):

wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh --name jammy

Fedora

amd64 (39):

wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh --name 39

Cross compilation on amd64 for developers

Using additional options you can cross compile locally --local: use a local hyperion source code directory rather than cloning from GitHub --incremental: do incremental compiles, Note: you need to keep the image and tag stable

Compile code in $HYPERION_HOME incrementally for Raspberry Pi 2/3/4 (Debian Bookworm)

cd $HYPERION_HOME
./bin/scripts/docker-compile.sh --local --incremental --architecture arm/v7 --name bookworm

The usual way

Debian/Ubuntu/Win10LinuxSubsystem

For Linux/Ubuntu(<= 21.10) - Qt5 based

sudo apt-get update
sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libasound2-dev libturbojpeg0-dev libjpeg-dev libssl-dev

Ubuntu (22.04+) - Qt6 based

sudo apt-get update
sudo apt-get install git cmake build-essential qt6-base-dev libqt6serialport6-dev libxkbcommon-dev libvulkan-dev libgl1-mesa-dev libusb-1.0-0-dev python3-dev libasound2-dev libturbojpeg0-dev libjpeg-dev libssl-dev pkg-config

For Linux X11/XCB grabber support

sudo apt-get install libxrandr-dev libxrender-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev

For Linux CEC support

sudo apt-get install libcec-dev libp8-platform-dev libudev-dev

on RPI you need the videocore IV headers

sudo apt-get install libraspberrypi-dev

OSMC on Raspberry Pi

sudo apt-get install rbp-userland-dev-osmc

Additionally for QT6 when QT6 installed separately on Ubuntu < 22.04

sudo apt-get install postgresql unixodbc libxkbcommon-dev

ATTENTION Win10LinuxSubsystem we do not (/we can't) support using hyperion in linux subsystem of MS Windows 10, albeit some users tested it with success. Keep in mind to disable all linux specific led and grabber hardware via cmake. Because we use QT as framework in hyperion, serialport leds and network driven devices could work.

Arch

See AUR for PKGBUILDs on arch. If the PKGBUILD does not work ask questions there please.

Fedora

The following dependencies are needed to build hyperion.ng on fedora.

sudo dnf -y groupinstall "Development Tools"
sudo dnf install python3-devel qt-devel qt5-qtbase-devel qt5-qtserialport-devel xrandr xcb-util-image-devel qt5-qtx11extras-devel alsa-lib-devel turbojpeg-devel libusb-devel xcb-util-devel dbus-devel openssl-devel fedora-packager rpmdevtools gcc libcec-devel

After installing the dependencies, you can continue with the compile instructions later on this page (the more detailed way..).

OSX

To install on OS X you either need Homebrew or Macport but Homebrew is the recommended way to install the packages. To use Homebrew, XCode is required as well, use brew doctor to check your install.

First you need to install the dependencies:

brew install git qt@5 python3 cmake libusb openssl@1.1

Windows

We assume a 64bit Windows 10. Install the following;

Optional:

Compiling and installing Hyperion

The general quick way (without big comments)

complete automated process for Mac/Linux:

wget -qO- https://raw.githubusercontent.com/hyperion-project/hyperion.ng/master/bin/compile.sh | sh

some more detailed way: (or more or less the content of the script above)

# be sure you fulfill the prerequisites above
git clone --recursive https://github.com/hyperion-project/hyperion.ng.git hyperion
cd hyperion
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make -j $(nproc)
if this get stucked and dmesg says out of memory try:
make -j 2
# optional: install into your system
sudo make install/strip
# to uninstall (not very well tested, please keep that in mind)
sudo make uninstall
# ... or run it from compile directory
bin/hyperiond
# webui is located on localhost:8090 or 8091

In case you would like to build with a dedicated Qt version, Either supply QTDIR as -DQTDIR=<path> to CMake or set an environment variable QTDIR pointing to the Qt installation.

On Windows MSVC2022 set it via the CMakeSettings.json:

  "configurations": [
    {
      ...
      "environments": [
        {
          "QTDIR": "C:/Qt/6.5.3/msvc2019_64/"
        }
      ]
    },

The detailed way (with many comments)

Download: Creates hyperion directory and checkout the code from github

export HYPERION_DIR="hyperion"
git clone --recursive --depth 1 https://github.com/hyperion-project/hyperion.ng.git "$HYPERION_DIR"

Preparations: Change into hyperion folder and create a build folder

cd "$HYPERION_DIR"
mkdir build
cd build

Generate the make files: To generate make files with automatic platform detection and default settings: This should fit to *RPI, x86, amlogic/wetek:

cmake -DCMAKE_BUILD_TYPE=Release ..

Developers on x86 linux should use:

cmake -DPLATFORM=x11-dev -DCMAKE_BUILD_TYPE=Release ..

To use framebuffer instead of dispmanx (for example on the cubox-i):

cmake -DENABLE_FB=ON -DCMAKE_BUILD_TYPE=Release ..

To generate make files on OS X:

Platform should be auto detected and refer to osx, you can also force osx:

cmake -DPLATFORM=osx -DCMAKE_BUILD_TYPE=Release ..

To generate files on Windows (Release+Debug capable):

Platform should be auto detected and refer to windows, you can also force windows:

# You might need to setup MSVC env first
call "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
cmake -DPLATFORM=windows -G "Visual Studio 17 2022" ..

Run make to build Hyperion: The -j $(nproc) specifies the amount of CPU cores to use.

make -j $(nproc)

On a mac you can use sysctl -n hw.ncpu to get the number of available CPU cores to use.

make -j $(sysctl -n hw.ncpu)

On Windows run:

cmake --build . --config Release -- -maxcpucount

Maintainer: To build installer, install NSIS and set env VCINSTALLDIR="C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC"

Install hyperion into your system: Copy all necessary files to /usr/local/share/hyperion

sudo make install/strip

If you want to install into another location call this before installing

cmake -DCMAKE_INSTALL_PREFIX=/home/pi/apps ..

This will install to /home/pi/apps/share/hyperion