You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any intention to support wasm32-unknown-unknown target? I've tried to target web assembly but there are current old or deprecated dependencies that don't support wasm32 looking at the cargo tree. How hard would it be updating or replacing some of the dependencies that use libraries like timerustc-serializememchr and support wasm?
The text was updated successfully, but these errors were encountered:
Because crfsuite-rs is just a binding of the C version of crfsuite. The steps to compile it are the following:
compile C code for a given target into a static library using the cc crate
convert header into rust code using bindgen
Which is basically what the crfsuite-sys crate does.
I successfuly compiled the static library for wasm32 target (at least I have an artefact), but I had a problem with bindgen to generate an API (no symbols were actually generated) which looks a lot like this issue rust-lang/rust-bindgen#751.
And even after hacking a bit this part (like trying to reuse a generated API from an other 32bit target). The linking part failed which could be whether the result of a bad compilation of the static library or something else I don't know.
In order word, I tried and I failed. But I have a strong feeling that is doable if we put enough time into it. And the first step to do so is to compile crfsuite-rs for wasm32 and any help are welcome on this! So feel free to open a PR if you have any idea on how to do it.
Is there any intention to support
wasm32-unknown-unknown
target? I've tried to target web assembly but there are current old or deprecated dependencies that don't support wasm32 looking at thecargo tree
. How hard would it be updating or replacing some of the dependencies that use libraries liketime
rustc-serialize
memchr
and support wasm?The text was updated successfully, but these errors were encountered: