-
Notifications
You must be signed in to change notification settings - Fork 4
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
What can I do with "too many errors" ? #12
Comments
Hello, no worries. Hmm, seems to be related to this bytecodealliance/wasmtime-go#192 (comment) (tl;dr: upgrading Go breaks the Windows wasmtime-go build?) Easiest way to get around it would be using WSL and building it in Ubuntu etc. Just tried it and I'm getting weird errors on regular Windows but WSL works. I might just switch this library to wazero which is written in Go and avoids the library dependencies that wasmtime has. It will be a little slower but a lot easier to build 🤔. For Stream the speed won't be issue because all (iirc) of the work happens during startup. |
cool, thanks for the info. yeah on mac i didn't have this issue with newest go version. |
The latest releases upgraded the wasmtime version so it (might) work better in Windows now. It fixes some other stuff too so might be a good idea to upgrade |
hi again @guregu 🫡 i'm having the same issue nowadays.. i have a special case where we require to use windows for sth and streamapi fails to build on it. is there something else i can/should try..? |
With the wazero switch this shouldn't happen anymore! |
@guregu hi! ~
could you help me resolve this? just trying
go build
for stream but getting stopped at these errors. haven't encountered this before. also just updated go version; if that matters. Windows 11.(sorry for posting here , but idk how else to contact you 😅 )
The text was updated successfully, but these errors were encountered: