-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows support? #69
Comments
Thanks! It seems like from the README that we may not support this on Windows yet -- once we do, we'll add it to our CI to make sure our installation instructions work on Windows too. I don't have context on the go extension at all right now. I have no idea if this is easy or hard to fix, perhaps it's something I can look into once I get the highest priority items off my todo list. In the meantime, you're welcome to take a crack at fixing it if you'd like. If you have context on Go on Windows, then you're more qualified to fix this than me! |
Hey, We are migrating our CI to Azure, so that we can start testing on Windows. |
@MarkMcCaskey Hey any luck getting it to work on Windows? I've been postponing my project since like last year. It would really mean a lot if this got fixed/added. Thanks. |
We will resume this work. |
Uncertain whether to label this issue a bug report or an enhancement.
I tried to make go-ext-wasm work in Windows by manually copying the 0.7.0 wasmer_runtime_c_api.dll to github.com\wasmerio\go-ext-wasm\wasmer.
Yet on seeking to run the example I receive Process finished with exit code -1073741515 (0xC0000135)
Is it possible to get go-ext-wasm running in Windows somehow? Or does the go extension currently not support Windows yet?
The text was updated successfully, but these errors were encountered: