Sam Clegg
Sam Clegg
These were generated using latest wasmtime release (0.16.0) and the wasi-sdk 10 release binaries.
Seems a little odd to me that they both fail in different ways, on this one tests, but all other tests pass. This is using the official wask-sdk-10.0 linux binaries:...
See https://github.com/WebAssembly/wasi-sdk/issues/117 Currently we build against `debian:stretch` inside a docker contains and hope for the best. We should probably document the minimal requires for libc, libc++ and any other dynamic...
Using these binaries then wouldn't require a `--target`. This is a relatively common pattern for cross compilers and it means you can put `wasi-sdk/bin` on the end of your `PATH`...
Right now the SDK consists of two main parts: 1. the wasi sysroot 2. a recent build llvm from stable branch In (2) list of llvm components we install is...
We could use circle-ci or travis-ci. They both allow for long builds like this now (travis limit is 50 minutes and I think circle-ci is 5 hours!). We could also...
As mentioned in https://github.com/CraneStation/wasi-sysroot/issues/70 it might make sense to integrate or unify the two current efforts we have to build wasm sdk. The https://github.com/WebAssembly/waterfall does have slightly different goals in...
If you are interested in filing a request for access to the Works on Arm test and CI infrastructure, please fill out the details below. Proposals will be evaluated on...