Unless you statically linked GTK, possibly Xorg, and more into a ludicrous bundle size, you’d still be screwed.
As for “just get the libs,” that’s hilariously easier said than done. Try my example - it’s enough to make an engineer cry.
As for “just get the libs,” that’s hilariously easier said than done. Try my example - it’s enough to make an engineer cry.
* if u dont sandbox this a bit with custom lib paths
What I am disputing is how this comes off to a game developer; 5 years from now, heck, 2 years from now when their games require library surgery to keep running... that’s just an awful experience.
That is not what a developer would consider a stable ABI. They could look into Flatpak - but look at what’s trending on Hacker News today - a rant against Flatpak.
Win32 over Proton is the winner for them; all other proposed solutions are hilariously naive and optimistic to what game development requires. No game developer is ever going to individually package, and consistently repackage, their game for 20 distributions. That’s never going to happen.
>No game developer is ever going to individually package, and consistently repackage, their game for 20 distributions. That’s never going to happen.
Nobody has suggested they should.
Nor do they. Steam Linux Runtime exists.
XLib is tiny by modern standards.
my memory might be wrong but I had issues with native linux games that had level editor based on GTK and python, could not get them to run after 3 years since launch, I do not claim it is impossible just that I could not do it with some a few hours effort.