Linux

54194 readers

534 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

[email protected]

Is there still any hope for static binaries (games) that "just work" across distros? (youtu.be)

submitted 1 month ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

Has anybody been able to build a statically linked binary that shows a Vulkan surface? I've put some context around this problem in the video. I understand that the vulkan driver has to be loaded dynamically - so it's more of a question whether a statically built app can reliably load and talk with it. I think it should be possible but haven't actually seen anyone make it work. I'm aware of "static-window9" by Andrew Kelley but sadly it doesn't work any more (at least on my Gentoo machine T_T).

(I'm also aware of AppImages but I don't think they're the "proper" solution to this problem - more like a temporary bandaid - better than Docker but still far from perfect)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 month ago (5 children)

Has anybody been able to build a statically linked binary

The question should by why you'd want to. Careful if your reply is something about 'one binary to work on a very diverse arrangement of library pinnings' because the next question would be 'why would you think that's either achievable or valuable as a goal'; and toss in a 'why try to ship the same binary in several different repos anyway' bonus question.

In short, if your biggest problem is how to build a binary that works everywhere, you have a lot of questions about responsible build/release processes to answer, and they will be embarrassing for you.

[–] unhrpetby 1 points 1 week ago

The question should by why you'd want to.

Because the application working is more important than the downsides in my case. Its quite useful for an application which hasn't been updated in a long time, will never receive updates again, or doesn't work in my nonstandard environment.

I have had older applications fail to function due to DLL hell.

load more comments (4 replies)