You are viewing a single thread.
View all comments View context
8 points

So, like, dumb question. People here assumed that I mean AppImages, whereas I actually meant just a statically linked binary. Is that really the only reason why AppImage exists? So, that dynamically linked applications can be distributed like statically linked ones?

permalink
report
parent
reply
9 points

You cannot statically link everything. Take graphics libraries and APIs for example, do you statically link against nvidia’s or mesa’s opengl?

permalink
report
parent
reply
2 points

Sure, but presumably AppImage/Flatpak/Docker cannot help with that either…?

permalink
report
parent
reply
3 points

This is the problem those tools try to solve. They package everything else upon which software might depend that can’t simply be linked into a single binary.

permalink
report
parent
reply
3 points

Flatpak solves the problem with targetable platform versions, you just update the manifest for your app every like 6-12 months to target the new one

permalink
report
parent
reply
6 points

The majority of AppImages I’ve seen have been dynamically linked, yes. But it’s also used for packaging assets.

permalink
report
parent
reply
3 points

Yeah, alright, packaging assets makes sense. I’ve always been fine with just a .tar.gz, but having it be a singular file without compression is cool.

I guess, since AppImage emulates a filesystem, you can also have your application logic load the assets from the same path as if the assets were installed on the OS, so that’s also cool.

permalink
report
parent
reply
2 points

You cannot statically link everything. Take graphics libraries and APIs for example, do you statically link against nvidia’s or mesa’s opengl?

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

Hint: :q!


Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules
2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of “peasantry” to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
4. No recent reposts
  • Everybody uses Arch btw, can’t quit Vim, and wants to interject for a moment. You can stop now.

Please report posts and comments that break these rules!

Community stats

  • 6.8K

    Monthly active users

  • 1K

    Posts

  • 20K

    Comments