Can't build WASM: System.Exception: Failed to run emscripten

[trydalch]

For some time now our WASM build has been broken. Not sure what caused it, but as we've not been developing for web (yet), we've left it untouched. Until now.

From the binlog, here's the final message that fails:

Running [C:\Users\[Username]\...\...\[Project]\obj\Debug\net8.0-browserwasm\workAot]: cmd /c call "C:\Users\[Username]\.uno\emsdk\emsdk-3.1.34\emsdk\emsdk_env.bat" 2>&1 && C:\Users\[Username]\AppData\Local\Temp\dotnet-runtime-wasm-windows-498e18e-7331dcb60e0-8790049905-Release-simd\tools\ninja.exe  -v

[00:00:00.0286732] The system cannot find the path specified.

When I check the .uno\emsdk\emsdk-3.1.34 folder, it's empty.

[trydalch]

Here's my binlog.
msbuild-redacted.zip

[trydalch]

2/3 of the paths exist. C:\Users\REDACTED__Username\.uno\emsdk\emsdk-3.1.34\emsdk\emsdk_env.bat does not. The folder exists, but there's no emsdk_env.bat file. The folder is empty.

[jeromelaban]

Thanks. For what I can tell, in the binlog you sent in #19087 (reply in thread), there already was a folder named C:\Users\REDACTED__Username\.uno\emsdk\emsdk-3.1.34:

Could you try deleting that folder and create a binlog immediately after that? To be sure you're not getting VS doing parts of it automatically, use the command line dotnet build -f net8.0-browserwasm /bl.

Thanks!

[trydalch]

I'm getting other odd errors when trying to build via CLI. I suspect it's because we're referencing some old-style .net framework projects and leveraging .Net Compatibility Mode. So I'm not sure I can do that. Looks like I'm limited to VS.

A quick aside: When I ran uno-check it prompted me to install the .net9 sdk, which I did. It now seems to be using that to build even though my project file is targeting .net8-*.

I've deleted the folder and then created a binlog immediately after and I'm still getting the same error. The .uno/emsdk/emsdk-3.1.34 is empty.

Here's the latest binlog.

msbuild-12.20.zip

[trydalch]

I think I've figured it out. I have python installed via pyenv-win, so the python that's in my path is another .bat file. This is causing the emsdk setup script to exit prematurely, even though there wasn't an error.

I changed the python --version line to:

CALL python --version

This caused the emsdk setup script to actually run to completion and my wasm build is now fixed.