Closed bhelx closed 5 months ago
install-wasi-sdk.sh
doesn't work because 1) it's a shell script, 2) windows doesn't have real CURL, it's mapped to Invoke-WebRequest. Should probably implement this as a .ps1 script for windowscd -
. The equivalents on Win are push-location and pop-location. I'm not sure if the cd -
is used to fix the pwd to always be correct in case the previous cd commands failed or if it's just a shorthand way to undo a previous cd. If the latter, this incompatibility could be fixed by just updating to cd ../..
and not using this syntax.I worked around these issues by
cd -
to cd ../..
in the cli and core scriptsinstall-wasi-sdk.sh
script manually
wasi-sdk
folder$env:QUICKJS_WASM_SYS_WASI_SDK_PATH = "C:/Code/js-pdk/wasi-sdk"
make
install.sh
script doesn't work because it's a shell script. need an equivalent .ps1 script or should be on Chocolatey
binaryen
needs to be installed manually
PS C:\Code\js-pdk\examples\simple_js> ..\..\target\release\extism-js.exe .\script.js -i .\script.d.ts
child not found in parent
UNREACHABLE executed at D:\a\binaryen\binaryen\src\passes\Precompute.cpp:838!
the built wasm file is callable, but that's the extent I've tested it.
..\..\extism.exe call .\index.wasm greet --input "Luke" --wasi
Hello, Luke!
@lukevp that's really good progress! I will try to see if we can package your findings and make things smoother for Windows users next week
I believe the tools we use support windows, so we just need to add windows to our CI and publish workflows:
But testing may yield some other issues.