libsodium/test/default/wasi-test-wrapper.sh

#! /bin/sh

if command -v wasmtime >/dev/null; then
  wasmtime -o --dir=. "$1" && exit 0
fi
if command -v wasmer >/dev/null; then
  wasmer run "$1" --dir=. && exit 0
fi
if command -v lucetc-wasi >/dev/null && command -v lucet-wasi >/dev/null; then
  lucetc-wasi \
    --min-reserved-size "128MiB" \
    -o "${1}.so" --opt-level best "$1" &&
    lucet-wasi --dir=.:. "$1.so" && exit 0
fi
Run the WASI checks using wasmtime 2019-04-08 12:45:08 -07:00			`#! /bin/sh`

Try wasmer and lucet as alternatives to wasmtime However: - wasmer seems to have issues with signals, causing some tests to fail - lucet's --dir option doesn't seem to work with relative paths These are temporary limitations, that are likely to be fixed soon. 2019-04-22 14:53:43 -07:00			`if command -v wasmtime >/dev/null; then`
			`wasmtime -o --dir=. "$1" && exit 0`
			`fi`
			`if command -v wasmer >/dev/null; then`
			`wasmer run "$1" --dir=. && exit 0`
			`fi`
			`if command -v lucetc-wasi >/dev/null && command -v lucet-wasi >/dev/null; then`
Lucet requires --min-reserved-size or tests with large allocations will fail 2019-04-22 16:13:25 -07:00			`lucetc-wasi \`
			`--min-reserved-size "128MiB" \`
			`-o "${1}.so" --opt-level best "$1" &&`
			`lucet-wasi --dir=.:. "$1.so" && exit 0`
Try wasmer and lucet as alternatives to wasmtime However: - wasmer seems to have issues with signals, causing some tests to fail - lucet's --dir option doesn't seem to work with relative paths These are temporary limitations, that are likely to be fixed soon. 2019-04-22 14:53:43 -07:00			`fi`