Install fails with no error message on Ubuntu Studio 20.04, build from source fails

[Brainpiercing]

Hello,
I'm trying to install the plugin pack on Ubuntu Studio 20.04.
The AppImage produces no response whatsoever, no error message.

OK I realize it's a GLIBC issue with 20.04 and trying to make it work doesn't seem like it's worth the trouble

I'm trying to build from source, but presently I can't because I can't change the Qt6 folder structure in the docker file or else the script fails because it's been modified.

Please help.

[Brainpiercing]

Ok I simply removed the check, but also symlinked my qt6 install from everywhere, and it continues the build.

I stopped it though when it started trying to install gnome, from what I can tell? I don't want gnome, why would it try to install it? Is there any way to get this to compile without?

[cannam]

It's very unfortunate that there's no feedback when an executable (like an AppImage) fails to run because of a library versioning problem.

To do a local build yourself, I wouldn't really advise using the Docker container scripts, which are designed to build and test an AppImage - all you really need is a normal executable built locally and to achieve this, it should be possible to run something like

$ ./repoint install
$ qmake6 -r
$ make -j3

to produce a binary called vamp-plugin-pack-installer which you can then run.

The qmake part may vary depending on what your Qt6 installation calls its qmake to distinguish it from Qt5's - if you use a Qt5 qmake, the qmake step will appear to work but the build will fail. And qmake may need an additional argument like QMAKE_RCC=/usr/lib/qt6/libexec/rcc (depending on where rcc actually lives) because qmake has a problem of failing to find its own rcc binary.

The reference to GNOME appears in the test container, just as a way to get a "normal desktop environment" installed without any specific Qt-related components, as a proper test for the AppImage.

Finally note that there are not actually all that many differences between the Vamp Plugin Pack v1.0 (still available for download at https://code.soundsoftware.ac.uk/projects/vamp-plugin-pack/files) and v2.0. The main difference I think is the addition of Expressive Means plugins. On older systems it may be easier to install the older version of the Pack and then add Expressive Means from https://github.com/cannam/expressive-means separately if desired.

[Brainpiercing]

Thanks a lot for your reply. I'm sorry it took me so long to reply, I was very busy and had to put this aside for a bit.

It's very unfortunate that there's no feedback when an executable (like an AppImage) fails to run because of a library versioning problem.

There actually is an error message - of sorts - when I run from command line, but I tend to want to open AppImage files directly from the GUI.

To do a local build yourself, I wouldn't really advise using the Docker container scripts, which are designed to build and test an AppImage - all you really need is a normal executable built locally and to achieve this, it should be possible to run something like

$ ./repoint install
$ qmake6 -r
$ make -j3

to produce a binary called vamp-plugin-pack-installer which you can then run.

I got that far... But as I said in my edit, the GLIBC with Ubuntu 20.04 is simply too old for this.

The reference to GNOME appears in the test container, just as a way to get a "normal desktop environment" installed without any specific Qt-related components, as a proper test for the AppImage.

OK thanks for that, I just wonder what random packages related to gnome I now have installed before I canceled the process ;)

Finally note that there are not actually all that many differences between the Vamp Plugin Pack v1.0 (still available for download at https://code.soundsoftware.ac.uk/projects/vamp-plugin-pack/files) and v2.0. The main difference I think is the addition of Expressive Means plugins. On older systems it may be easier to install the older version of the Pack and then add Expressive Means from https://github.com/cannam/expressive-means separately if desired.

I will most definitely try that! Thanks!