wasm2c does nothing at all about wabt

[keithw]

Hmm... "it works in CI." If you can bisect this, that might be helpful, or if other Windows users are affected, maybe you can help each other try to figure out what's happening. I am tempted to have us stop publishing binary releases on GitHub since they seem to cause a lot of trouble (and it's not really our core competency -- seems like Homebrew/Debian/the Windows equivalent are probably better at building and publishing binary releases for all these architectures than we are).

Not saying it's not a bug somehow, just that beyond building and testing in CI, I suspect we're not going to be at our best trying to debug an issue with the binary Windows release. (Does it work if you compile from source? Or does the Linux release work for you in WSL?)

[keithw]

Closing as dormant. Please feel free to respond and we can reopen (or if anybody else is having this problem, please also speak up).

[Photosounder]

Did you even try running the program yourself? If you break something on Windows and aren't interested in investigating it then you're effectively dropping Windows support.

[keithw]

No -- my only access to Windows is via the GitHub CI environment where wasm2c apparently continues to work. (And I assume Firefox tests wasm2c in their CI environment when they update.) I'm not sure we "support" any platform per se, but if you respond to some of the questions in my original reply we can help investigate. It would be useful to know how broadly Windows users/configurations are affected and perhaps we can look for some commonality between your setups.