Chris Waldon <christopher.waldon.dev@gmail.com> wrote

> I'm fairly sure you could build a statically-linked cage that only
> dynamically depended upon system GL libraries.

While I'm not sure how to do it, I at least understand the words.  But here

> You could then bundle that compositor, your application binary,
> and a script that started them together into a self-contained
> executable so that the user could still only have a single file
> to worry about.

you lost me already at "your application binary" how would I get this?
Or is it simply `GOARCH=arm GOOS=linux go build ...` and gio
chooses the driver at runtime? Care to elaborate?  Or has anyone
done this successful for an rpi3?

Thanks a lot to everyone for this very portable go gui library!

Best Stephan