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

Gate WASM module behinde feature flag #27

Merged
merged 1 commit into from
Jul 12, 2024
Merged

Conversation

alerque
Copy link
Contributor

@alerque alerque commented Jul 10, 2024

This isn't tested yet, but it's roughly what I think would address my problem and close #26.

@alerque
Copy link
Contributor Author

alerque commented Jul 10, 2024

If you'd prefer this can probably be adjusted to be gated both ways such that WASM is a feature but on by default and further gated by the target. For most people that would mean not having to change their build arguments from what they are now, and allow me to use no-default-features to disable it.

@alerque
Copy link
Contributor Author

alerque commented Jul 10, 2024

I just tried building on my side with a Git dependency pointing at this branch and it does seem to have resolved by duplicate symbols linker problem. That doesn't mean I didn't break anything else, but it does seem to fix the problem.

@wezm wezm force-pushed the wasm-as-feature branch from e8052cd to 7f2f08e Compare July 12, 2024 08:48
@wezm wezm merged commit 0187b2e into wezm:master Jul 12, 2024
6 checks passed
@alerque alerque deleted the wasm-as-feature branch July 12, 2024 13:07
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.

Make WASM compilation an optional feature
2 participants