Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a statically linked package #83

Open
jzbor opened this issue Sep 3, 2024 · 3 comments
Open

Provide a statically linked package #83

jzbor opened this issue Sep 3, 2024 · 3 comments

Comments

@jzbor
Copy link

jzbor commented Sep 3, 2024

I noticed that my CI takes a lot of time downloading dependencies for deadnix (namely libgcc, glibc and their dependencies). I think this could be avoided by using a binary that is statically linked against musl. Ideally this could be provided as a flake output.

@astro
Copy link
Owner

astro commented Sep 6, 2024

Though I got rid of naersk, I am failing to build with pkgsCross.musl64.pkgsStatic.

Cross-building deadnix from nixpkgs works, however. Would you like me to switch deadnix-action to that?

@jzbor
Copy link
Author

jzbor commented Sep 9, 2024

I didn't even know of deadnix-action. Currently I use deadnix from nixpkgs, so just using that might work. One thing is, that it will not be cached like the default package.

I think the best solution would be a deadnix-static package so it could make use of the public binary cache, but I think this might not align with nixpkgs packaging guidelines.

@jzbor
Copy link
Author

jzbor commented Sep 23, 2024

So I have now successfully created a static build with crane. Sadly however the benefit seems to be negated by the usage of flakes, as their download takes almost as long as downloading libc + dependencies (see here).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants