Arch Linux User Repository

I actually am the upstream maintainer, so...

But unfortunately, no, there isn't any way to speed up the compilation. Compilation takes 20 to 30 minutes for me. It's slow because github.com/diamondburned/gotk4/pkg/gtk/v4 and related packages are wrappers around C libraries, so it has to invoke the C compiler. Go itself is already doing stuff concurrently, namely compiling packages in parallel with each other that can be based on what their dependencies are, but there's not much it can do when it runs into the C dependencies to speed up those specific ones. It does cache them, but if it's been ejected from the cache since the last time, or you upgraded to a new version of Go, or something else in the environment has changed that requires a recompile, well... I think makepkg's system also breaks the cache, as it seems to always need to recompile whenever I'm testing the PKGBUILD.

That's one of the reasons that I also have a Flatpak available, as that's precompiled.

This may be a question for upstream, but is there a way to enable multithreaded compilation for the Go dependencies? github.com/diamondburned/gotk4/pkg/gtk/v4 takes forever and it seems to only use one core.

Have you installed the base-devel group manually, @hmnd?

On a new Manjaro install, I got the bellow error when trying to install. I think pkgconf should be added to makedepends.

pkg-config: exec: "pkg-config": executable file not found in $PATH

Thanks! One fewer thing I have to accept the architecture difference on.

Yeah, it should. While it's true that I can't really test it myself, the Flatpak has explicit support for aarch64 and the app doesn't really do anything that's likely to cause it to fail because of an architectural difference, so I guess that I'll enable it.

This appears to work fine on my aarch64 machine, with no changes to the pkgbuild required. I understand if you don't wish to claim compatibility with an architecture you cannot test with however.