t4chib4ne

If you don't require running torbrowser under X you can have it running under wayland natively instead. For testing you could run the following from the commandline: ``` $ MOZ_ENABLE_WAYLAND=1...

Sorry that I wasn't patient enough to wait for flouthocs comment but I dug around a little in the wasmtime c-api and was able to get a basic WASM component...

Hm ... I guess it would make sense. I will do some cleanup and try implement missing features most notably argv is currently not passed to the component.

So I wanted to implement the `wasi_config_preopen_dir` for WASIp2 by first trying to write something to the filesystem with WASIp1 which resulted in a permission denied error. The reason is...

Thanks for taking a look, hope I didn't oversee anything! The only thing keeping this PR as a draft is that I would like to give both WASM modules and...

I marked the PR as a draft again because I don't want to trigger CI all the time. There is also a bigger change in the works which cleans up...

> @t4chib4ne the tests are not happy. @giuseppe is that expected? I saw that but they failed because of a failed provisioning of the test environment due to an [outage](https://status.testing-farm.io/issues/2025-10-18-provisioning-unstable-in-testing-farm-public-ranch/)....

I wrote an [ebuild](https://github.com/t4chib4ne/tachibane-overlay/blob/main/dev-libs/wasmtime/wasmtime-37.0.2.ebuild) (Gentoo) and installed it that way. It just downloads a release from the repo you linked, configures `-DBUILD_SHARED_LIBS=yes` and `-DWASMTIME_FASTEST_RUNTIME=yes`, adds a SONAME to the lib...

Sorry for spamming but I think I found the issue: wasmtime 37 and 38 still ship `wasip2.h` thus when building from release still compiles. When using the wasmtime main branch...

Should be good to review now, @flouthoc I tested against wasmtime 37 and the `release-39.0.0` branch.