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

Statically link libs for general Linux #93

Merged
merged 2 commits into from
Jul 26, 2024
Merged

Statically link libs for general Linux #93

merged 2 commits into from
Jul 26, 2024

Conversation

suhaibmalik
Copy link
Contributor

The docker image as-is requires the host to have libraries. Recommend statically linking them instead so that it works across environments.

@mycrl mycrl merged commit 21ef158 into mycrl:main Jul 26, 2024
1 check passed
@mycrl
Copy link
Owner

mycrl commented Jul 26, 2024

The docker image as-is requires the host to have libraries. Recommend statically linking them instead so that it works across environments.

I don’t use docker much, so I don’t know the difference.
But isn’t the docker image itself cross-platform? Why do I need to deal with cross-platform differences?
I merged the change anyway.

@suhaibmalik
Copy link
Contributor Author

Thanks!

Docker still piggyback's off of the host system for certain things since it's not a VM/OS. Assuming that the docker container was running fine on your end, it was probably getting the correct glib references thru your host.

In this case I'd say it's more due to Rust's compiler's design decision to assume that glib is going to be available in the runtime environment.

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

Successfully merging this pull request may close these issues.

2 participants