Antoine Lavandier (Nov 20 2025 at 10:57): Antoine Lavandier (Nov 20 2025 at 10:57):The wasi feature of wasmtime requires a dependency on the standard library which is to be expected. There are some parts of wasi I would like to be play with for testing. What's the best way to keep the wasi parts that are (easily made) no_std compatible and ditch the rest ? Is the wasi feature absolutely required to run files compiles to the wasm32-wasipX targets or can this be done through the component model ?
My first idea would be to
wasm32-wasipX.wasm from the unused wasi symbolscomponent-model feature and create an Host Struct that implements some subset of wasi and stubs the restWould that work ?
Alex Crichton (Nov 20 2025 at 15:40):The wasmtime-wasi-io crate is designed to compile to no_std, but otherwise wasmtime-wasi and wasmtime-wasi-http are unlikely to compile to no_std. That being said you can always generate your own wasi bindings and implement (or stub) the APIs yourself to implement in a no_std environment
Notification Bot (Dec 04 2025 at 17:34):Andrew Brown has marked this topic as resolved.
Notification Bot (Dec 04 2025 at 17:36):Andrew Brown has marked this topic as unresolved.
Last updated: Dec 06 2025 at 06:05 UTC