clockworklabs / clockworklabs/SpacetimeDB
The module binding code compile to wasm failed.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
I try to use Dioxus and SpacetimeDB together. Dioxus compile rust code to wasm and run in browser.
The module binding code compile failed, because of the openssl crate can't compile to wasm.
a lot of errors like this:
[cargo] error[E0412]: cannot find type `c_int` in this scope
--> /Users/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/openssl-sys-0.9.107/src/./obj_mac.rs:752:33
|
752 | pub const NID_setct_CapReqTBSX: c_int = 545;
| ^^^^^ not found in this scope
|
help: consider importing one of these type aliases
I found the pr about wasm: https://github.com/clockworklabs/SpacetimeDB/pull/1700
Does it means that I have to wait the pr be merged, or any other way?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR 1700 and the reported openssl-sys compilation errors in the issue. Reproduce the Dioxus module binding build for wasm, then compare its dependency path with the PR. Done means the module binding code compiles to wasm without the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- build-system, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100