Closed minamz closed 3 weeks ago
Hello, no worries. Hmm, seems to be related to this https://github.com/bytecodealliance/wasmtime-go/issues/192#issuecomment-1734252302 (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.
good to know at least it was not some messup on my side~
probs no one on our side needs a windows fix for development atm anyway; feel free to close this i guess but pls do let us know if you update things ~
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. i have tried the following go versions: 1.22.~ 1.21.0 1.21.12
is there something else i can/should try..? thanks in advance
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 😅 )