Beiträge von sPOiDar

Zitat von Lord-Grey

a) To compile a local checked out hyperion.ng repository in a docker container, I tested a while ago.

Here is is modified script https://ufile.io/gtt43pv1

The problem with this script is that it assumes that all the dependencies are already present in the image, which is what caused me some consternation trying to get a build going.

Zitat von Lord-Grey

Would you mind sharing the hyperion.ng documentation sites which still makes references to QT4?
That would get us in the position to have it fixed....

Well, this is quite embarrassing - I think the QT4 lib errors were from an older build. However, the current debian package control file does not specify any dependencies, so installing it does not prompt to install the required libs. Also, the version number in the control file for the betas is just 2.0.0 with no suffix, which means that upgrades won't work from a repository.

Zitat von Awawa

docker scripts are in hyperion.docker-ci repo

Ah, so that's where the Docker base images live.

Zitat von Awawa

I've got quite opposite feelings. Debian Buster with Qt5 is already supported. No need to hack

It's clearly straight-forward if you're running Debian, but there're hoops to jump through for Ubuntu: modify Dockerfile from hyperion.docker-ci to build base image with deps; modify docker-compile.sh from main repo to use local image. And that's provided you know where to find them, which I couldn't find in any of the docs.

The binary packages suggested in the primary documentation on the website certainly do not work, as they're still based on the old QT4 build (for stretch I guess?).

hyperion.ng is what I was referring to here.

This is marked as solved, however the problem described appears to be valid. Since QT4 has been deprecated and is no longer available on Ubuntu 20.04, the precompiled binary packages on the release page do not work, as they're linked against a number of QT4 libs.

In addition, the docker compilation script in the repo does not allow targeting Ubuntu, as it requires custom base images with all the deps pre-installed, and the Dockerfile for those images doesn't appear to be in the repos.

In the end I managed to hack together a build script by combining the documentation on manually building, slotting it into a hacked docker-compile.sh script, and adding deps that were missing from the docs, until it compiled successfully.

Not an enjoyable process though - debs for multiple host environments added to CI would certainly be a welcome change.