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

Static binary builds #40

Closed
dbrgn opened this issue Feb 11, 2018 · 16 comments
Closed

Static binary builds #40

dbrgn opened this issue Feb 11, 2018 · 16 comments
Assignees

Comments

@dbrgn
Copy link
Collaborator

dbrgn commented Feb 11, 2018

Create binary releases for people without Rust / Cargo.

@dbrgn dbrgn self-assigned this Feb 11, 2018
@dbrgn
Copy link
Collaborator Author

dbrgn commented Feb 13, 2018

Linux should be easy, but the question is how to create macOS releases without having access to Apple hardware...

@Dod9er
Copy link

Dod9er commented Feb 13, 2018

@dbrgn
Copy link
Collaborator Author

dbrgn commented Feb 13, 2018

@Dod9er my computer is actually cross compiling different static linux binaries right now (using the rust-musl-cross docker image) 🙂 I will upload them as Github release later.

Regarding cross-compilation for macOS, maybe it could be done through TravisCI, which offers macOS targets.

@Dod9er
Copy link

Dod9er commented Feb 13, 2018

I think yes, macOS is listed here (never tested as I´m on linux): https://github.com/japaric/trust

dbrgn added a commit that referenced this issue Feb 13, 2018
@dbrgn
Copy link
Collaborator Author

dbrgn commented Feb 13, 2018

Linux binary releases: https://github.com/dbrgn/tealdeer/releases/tag/v1.0.0

dbrgn added a commit that referenced this issue Feb 27, 2018
@dbrgn
Copy link
Collaborator Author

dbrgn commented Feb 27, 2018

The script was updated to add a step that strips the binaries, making them considerably smaller (x86_64 is 44% smaller, arm is 47% smaller).

I won't replace the binaries (releases should be immutable), but it would be nice to add an 1.0.1 release with macOS and Windows builds (maybe through Travis / Appveyor).

@jdvr
Copy link
Contributor

jdvr commented Aug 21, 2018

Current version 1.0.0 is 13 commits above from master, It would be possible to generate a new one?

@dbrgn
Copy link
Collaborator Author

dbrgn commented Aug 21, 2018

@jdvr if you look at the commits, it's all README changes and configfiles 🙂

@jdvr
Copy link
Contributor

jdvr commented Aug 21, 2018

@dbrgn Next time I will check commits. sorry

@dbrgn
Copy link
Collaborator Author

dbrgn commented Aug 21, 2018

@jdvr no worries 🙂

@gd4c
Copy link

gd4c commented Nov 23, 2020

Any chance for Windows binaries?

@dbrgn
Copy link
Collaborator Author

dbrgn commented Nov 23, 2020

@gd4c someone would need to set up a CI configuration that outputs x86_64 Windows binaries as build artifact. I only rarely use Windows myself, so it doesn't have high priority for me at the moment.

However, things have gotten easier since we have switched to GitHub actions in the meantime. It probably wouldn't be too hard to create a Windows build artifact for every tagged release.

@gd4c
Copy link

gd4c commented Nov 24, 2020

That would be great! Thanks.

@dmaahs2017
Copy link
Contributor

@dbrgn @niklasmohrin this workflow (see gist) is what I use on my personal projects to release OSX, Windows, and Linux static binaries. Maybe this could be useful here

@niklasmohrin
Copy link
Collaborator

@dmaahs2017 Although I would rather not use any actions from authors other than actions and actions-rs, I have to admit that these actions seem convenient. Thanks for the hint 😄

@dbrgn
Copy link
Collaborator Author

dbrgn commented Jan 1, 2022

Fixed by #240. Binaries for macOS and Windows are now provided as well.

@dbrgn dbrgn closed this as completed Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants