Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
LMA1980 opened this issue Nov 23, 2024 · 0 comments
Labels
needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners untriaged New issue has not been triaged by the area owner

Comments

@LMA1980
Copy link

LMA1980 commented Nov 23, 2024

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-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 23, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

1 participant