AOT: dotnet-setup.sh fails to fully execite (python missing using WSL)

[assassin316]

Executing the dotnet-setup.sh script to install emscripten in the WSL command prompt almost fully completes but fails with an error related to python:

I attempted to fix it by installing python2, python-is-python3, but nothing worked

[assassin316]

UPDATE:

May be linked to this:

unoplatform/Uno.Wasm.Bootstrap#709

[jeromelaban]

Thanks for the update. Can you still provide a binlog? There's probably another error.

[assassin316]

Not sure if this is the culprit, but I found this in the log:

binlog.zip

[jeromelaban]

Thanks for the update. It seems that your csproj contains an invalid option, as seeing this command line:

[00:00:04.4527746] powershell "$env:PYTHONUTF8=1; emcc  -DENABLE_METADATA_UPDATE=1 -s USE_ZLIB=1 -s FORCE_FILESYSTEM=1  -fwasm-exceptions -DGEN_PINVOKE -IC:/Users/assas/AppData/Local/Temp/dotnet-runtime-wasm-windows-585dcd7-7db1c333330-4019238418-Release/runtimes/browser-wasm\native -emit-llvm  -lidbfs.js -l idbfs.js   -IC:/Users/assas/AppData/Local/Temp/dotnet-runtime-wasm-windows-585dcd7-7db1c333330-4019238418-Release/runtimes/browser-wasm/native/include/mono-2.0 -Oz -c -o corebindings.o corebindings.c"

Specifically -lidbfs.js -l idbfs.js, which seems to indicate -l idbfs.js which should be removed from your csproj as it's automatically added by the uno bootstrapper.

[assassin316]

As well, on a side note, the docs might need a small update:

https://platform.uno/blog/build-net-aot-for-webassembly-in-visual-studio-with-uno-platform/

Specifically here so that others don't encounter this issue like I did, Step 6 seems to be no longer needed.

[jeromelaban]

I see.

This particular article very old, and is not in the docs. The doc is mostly talking about AOT compilation here: https://platform.uno/docs/articles/external/uno.wasm.bootstrap/doc/runtime-execution-modes.html#runtime-execution-modes.

We can certainly link to more recent docs instead.

[assassin316]

It worked!! Thank you!

So the AOT build seems to be working as intended 👍

My last question regarding this is related to memory:

Where can I increase the memory for emcc?

According to the link below, there is a flag that can be specified: -s TOTAL_MEMORY= but since the uno bootstrapper adds the flags automatically, can we override it?

https://stackoverflow.com/questions/63595167/wasm-ld-error-initial-memory-too-small-18317952-bytes-needed

[jeromelaban]

Thanks for the update!

You can use this option to add the missing flag.

[assassin316]

Worked!