Stream: general

Topic: ✔ Adapt a wasm32-wasi build to wasm32-unknown-unknown


view this post on Zulip Geoff Goodman (Feb 08 2024 at 01:43):

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.

view this post on Zulip Geoff Goodman (Feb 08 2024 at 13:07):

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.

view this post on Zulip Notification Bot (Feb 08 2024 at 13:07):

Geoff Goodman has marked this topic as resolved.


Last updated: Nov 22 2024 at 17:03 UTC