WasmEdge 0.10.0 not working in windows

[Puellaquae]

Description

wasmedge.exe output nothing and exit with code -1073740791. Version 0.10.0, 0.10.0-rc.1, 0.10.0-alpha-2 in releases all not work.

Current State

Expected

Environment

Windows 10 Pro 21H2 19044.1706

Steps to Reproduce

just exec wasmedge.exe

[juntao]

Can you attach the wasm file you are trying to run? Thanks.

[Puellaquae]

No need to attach wasm file. Runing in linux without arguments will show usage, but in windows, usage also can't show.

[calvin2021y]

this project need run ci pipeline tests for windows/macOS/linux before release.

[hydai]

Hi @Puellaquae

The current CI uses Windows Server 2022 with Windows 10 SDK 19041 to build WasmEdge on Windows. And I just run the WasmEdge on my Windows 11.

Not sure if this issue is related to the version of windows. When I setup a new Windows 10 environment, the WasmEdge failed with msvcp140.dll is missing. So I follow the guide on the Windows forum to fix it.

https://answers.microsoft.com/en-us/windows/forum/all/msvcp140dll-and-vcruntime140dll-missing-error-only/6eeb77ea-3ed3-4b2b-ab8a-26fa6a0fc121

Maybe we need to set the MIN_TARGET_OS_VERSION to make the Windows build uses older msvcp version. Still need time to figure it out.

[hydai]

Thanks, @Pospelove provided an awesome PR #2455 to fix this. However, the LLVM we used(llvm-windows) currently doesn't offer the MT mode. If we applied #2455 would make the Windows CI fail. I kept the variable CMAKE_MSVC_RUNTIME_LIBRARY, so users can set it to "MultiThreaded$<$<CONFIG:Debug>:Debug>" with disabling the AOT feature while building WasmEdge to avoid msvcp140.dll issue.

Currently, we are looking for how to make an MT mode LLVM. Before this is fixed, I will keep this issue open.

[hydai]

WasmEdge 0.14.0 can now be executed on Windows. Closing this.