this post was submitted on 28 Apr 2024
18 points (100.0% liked)

Linux

8061 readers
61 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
[email protected]
18
Creating a self-contained binary (www.github.com)
submitted 6 months ago by [email protected] to c/[email protected]
5 comments fedilink hide all child comments
 

I have a program (fldigi, pointed to by the github link) that uses dozens of shared libraries. I would like to be able to distribute a pre-compiled version of the program for testers. I could require each tester to install the shared libraries and compile the program for themselves, however, this would be extremely difficult for most users. What are some options for distributing a pre-compiled version of a linux program? Do I need to make a package for common distributions or common versions of each distribution? How about snap, nix, or flatpak? I don't have much experience with using docker or preparing docker containers, and the particular program (fldigi) requires access to system hardware to function, which a containerized version would have to accommodate.

This is going to be a temporary solution and I hope once the program is done being tested, my changes can be pulled upstream and then distributions will include it that way.

top 5 comments
sorted by: hot top controversial new old
[–] [email protected] 20 points 6 months ago (1 children)

Just statically link the libraries

[–] [email protected] 1 points 6 months ago (1 children)

The problem is that I don't have static versions of most of the libraries available.

[–] [email protected] 4 points 6 months ago

Not with that attitude.

[–] [email protected] 12 points 6 months ago

Seems like one of the few good use cases for AppImages.

[–] [email protected] 0 points 6 months ago

I'd go with Nix, but I may be biased by my enthusiasm for Nix