How wasi 0.2 can be supported by a WebAssembly engine?

[zherczeg]

It looks like the interface is described in .wit files.

How can I compile these .wit files to WebAssembly? I only need the interface. Is there a python script for that?

Before implementing a function, I need to see its interface in a module. The preview1 interface clearly show the structure of functions, but I cannot find that anymore.

I saw something about so called components, but it looks like a complex system, which takes months to implement. So I would just prefer supporting wasi 0.2 in regular WebAssembly modules.

Thank you for the answer!

[zherczeg]

I have another question: Why these test directories are empty:
https://github.com/WebAssembly/WASI/tree/main/proposals/io/test

WebAssembly text modules (.wat files) could also be used to figure out the actual interfaces.

[ricochet]

Compiling wit to WebAssembly:

wkg wit build --wit-dir ./proposals/cli/wit
WIT package written to wasi:cli@0.2.9.wasm

# see it as wit
wasm-tools component wit wasi:cli@0.2.9.wasm

Useful tools:

• https://github.com/bytecodealliance/wasm-tools/tree/main/crates/wit-component
• https://github.com/bytecodealliance/wasm-tools/tree/main/crates/wit-dylib
• https://github.com/bytecodealliance/wasm-pkg-tools

We package the wit as a .wasm and then publish to OCI as part of this project's release pipeline: https://github.com/WebAssembly/WASI/blob/main/.github/workflows/publish-proposal.yml#L57-L62

It looks like those test directories need to be removed and were created as part of the original template 10 years ago. Tests are together at https://github.com/webassembly/wasi-testsuite

WASIP2 builds on top of the Component Model proposal. For something more similar to p1 with a c-abi style, there's proposed ways to build that tooling but nothing fully-functional that I'm aware of, see WebAssembly/component-model#378.

[zherczeg]

Thank you. The dump of wasi:cli@0.2.9.wasm is 6000 lines, will take some time to understand what is happening here.