search

flathub / com.github.wwmm.pulseeffects

https://flathub.org/apps/details/com.github.wwmm.pulseeffects
11 stars 6 forks source link

(Don't merge) Add note about easyeffects #53

Closed vchernin closed 2 years ago

vchernin commented 3 years ago

Made some maybe helpful comment so I could see if it still builds as this couldn't build locally.

flathubbot commented 3 years ago

Started test build 52826

flathubbot commented 3 years ago

Build 52826 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/50805/com.github.wwmm.pulseeffects.flatpakref
vchernin commented 3 years ago

I wonder why buildbot succeeds but flatpak-builder on my local machine (Fedora 34 Silverblue toolbox) doesn't? I was under the impression that Flatpak should avoid these problems by letting one have a consistent environment, but apparently here that wasn't the case.

I'll try to take a look again at this later.

Maybe I somehow made a mess of my toolbox setup or something.

hfiguiere commented 3 years ago

what's the error? flatpak-builder runs on the host, not in the sandbox.

vchernin commented 3 years ago

Earlier I was getting this:

[128/507] Generating giomm-credentials.cc with a custom commandError: module glibmm: Child process exited with code 137

Build bot's log showed [128/507] Compiling C++ object glib/glibmm/libglibmm-2.4.so.1.3.0.p/meson-generated_.._threads.cc.o

Now I get:

Error: module boost: Child process exited with code 137

I am not sure what is wrong with my system, I tried recreating the toolboxes and also install flatpak-builder on the host system. It's definitely a specific issue to my install as it built just fine in a Ubuntu 21.04 virtual machine by just installing flatpak-builder through apt as normal. It's probably some weird quirk with silverblue or something strange that I've broken.

Actually it may just be a cpu threading problem according to this thread. I'll try again later.

wwmm commented 3 years ago

module boost: Child process exited with code 137

We do not use boost anymore. If you have no other reason to compile it you can remove it.

glib/glibmm/libglibmm-2.4.so.1.3.0

The glibmm for gtk4 is glibmm-2.68

wwmm commented 3 years ago

You can also remove gstreamer libraries from the dependencies if you did not do that yet.

wwmm commented 3 years ago

The pkgbuild I use on Arch Linux should give an idea of what is needed https://github.com/wwmm/easyeffects/blob/master/PKGBUILD

vchernin commented 2 years ago

Not needed anymore, see https://github.com/flathub/com.github.wwmm.pulseeffects/issues/44