Replies: 1 comment 5 replies
-
I would not recommend using flatpak, snap or any other way to statically package your bevy game and used environment. Program which requires access to native graphics drivers will most likely require including them alongside your statically packaged program which automatically removes ways to use it outside of your own hardware or using it in general since you can't statically link/package drivers. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is it possible to Flatpak a Bevy app? Would I want to? Are there any considerations?
I have Flatpaked maybe three GTK apps, so I know a bit about it, but I just followed a tutorial then and don't understand it fully.
The first issue I ran into when looking into Flatpak for Bevy is the application identifier. In GTK you set it when you spawn the window, and I believe a correct identifier is a requirement for it to work properly? I can't figure out how to set the application identifier when using Bevy.
I'm not looking for a tutorial as those already exist (though a Bevy-specific one would be a great asset), I'm more interested in Flatpak from the perspective of a Bevy user.
Beta Was this translation helpful? Give feedback.
All reactions