With wasi-experimental, could not find wasi-sdk when trying to publish wasi-wasm console application error - a workaround proposal

[LMA1980]

When trying to publish a wasi-wasm console app.

We may be affected by the following error .dotnet/packs/Microsoft.NET.Runtime.WebAssembly.Wasi.Sdk/9.0.0/Sdk/WasiApp.targets(116,5): error : Could not find wasi-sdk. Install wasi-sdk and set $(WASI_SDK_PATH) . It can be obtained from https://github.com/WebAssembly/wasi-sdk/releases SDK is required for building native files.

This is related to the closed issue #94671.

I found out after reading the WasiApp.targets its looking for ${WAIS_SDK_PATH)/VERSION24 which is missing when using this install method.

The simple workaround is to do touch $WASI_SDK_PATH/VERSION24.

Hopefully this may help either find a permanent solution or provided appropriate documentation.

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

[pavelsavara]

Note WASI is experiment, so we are not going to fix this in Net9 and eventually we could get to improve it in Net10.

Creating $WASI_SDK_PATH/VERSION24 file by hand is correct workaround.

[itsMartinDev]

Solved this using WASI_SDK_PATH=C:\WebAssembly\wasi-sdk\wasi-sdk-24.0-x86_64-windows (as a custom path to have the sdk), but had to create an aditional folder called version24, and copy and paste folders (bin, lib, share) being duplicated.

Windows 10
Processor Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz 2.90 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor

[LMA1980]

Using Linux here. Can't tell about Windows experience. Will further investigate to determine if my proposal actually break things. Maybe a few symbolic links could be required to replicate the fix described by @itsMartinDev.

Before submitting my proposal, I did confirmed the tools was able to compile the basic template first. And be usable.

The test I did does not fully cover the suite.