Skip to content

wasm2c: update Windows build to always use internal sha256 library to resolve libcrypto DLL not found issue #2611

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

silbinarywolf
Copy link

Fixes #2609

Copy link
Member

@sbc100 sbc100 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really know enough about windows to know if this is the correct change.

Are you saying that Windows version prior to 11 do ship libcrypo.dll by default but Windows 11 does not? Its a little supprising to me that MS would break existing programs by making a change like. Do you have any links to information about this change?

@shravanrn @keithw do either you use windows much? Did you know anything about this issue?

@keithw
Copy link
Member

keithw commented Jun 2, 2025

I don't use Windows myself, but I think this libcrypto stuff has been causing us enough trouble (on platforms that are maybe not as strong at versioning/managing dependencies) that we should probably just switch to an always-vendored BLAKE3 hash for this and ditch the external library. I'll send a PR on this.

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.

The wasm2c command has no effect
3 participants