-
Notifications
You must be signed in to change notification settings - Fork 2
Support wasm32-wasip1 as a target
#31
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
Conversation
e552279 to
968c722
Compare
ruzstd instead of zeekstdwasm32-wasip1 as a target
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't need a wasm-compatible writer for now, only reader, but if it's easy to support as an option, that's good
|
What about other targets, that are neither x86_64, nor wasm32? E.g. aarch64, etc. |
|
A valid comment. I'll change it so that we fall back to the rust rewrite of |
694c5df to
688a563
Compare
alehander92
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, seems that now it should preserve the old behavior with no wasm
just need to update the vesion in Cargo.toml
4c32397 to
1a16f67
Compare
|
merging: @nickysn reminded us correctly to test if zeekstd works with aarch64: TODO separately |
This PR rewrites our compression logic to use
ruzstdinstead ofzeekstd, since ruzstd can be build for wasm targets