Given a crate that only targets wasm32-wasi (it wraps quickjs which is a c project), how might I go about wrapping / adapting the wasm32-wasi
build into a wasm32-unknown-unknown
build. I intentionally don't want any I/O except host functions I'll explicitly pass in so I don't think I'm really looking to virtualize things.
I'm also interested in pursuing approaches that will produce smaller file sizes.
A break from the computer and I realized that the wasm32-wasi
target does not produce a component in the first place :face_palm:. I can see the imports for preview1. Time to track down what's pulling in those bits of libc.
Geoff Goodman has marked this topic as resolved.
Last updated: Dec 23 2024 at 12:05 UTC