[WASI] testing code outside of the current repo
@lewing is already working on this.
Since Oct 3, 2024.
Assessment
This issue has not been assessed yet.
Description
Description
This doc https://github.com/dotnet/runtime/tree/main/src/mono/wasi#how-to-build-the-runtime suggested that built runtime pack can be referenced outside of the repo by a sample project. When I use it this way I end up with some errors:
hello-wasm failed with 1 error(s) (0.7s) → bin/Debug/net9.0/wasi-wasm/publish/
/home/jstur/.dotnet/nightly/packs/Microsoft.NET.Runtime.WebAssembly.Wasi.Sdk/9.0.0-rtm.24480.7/Sdk/WasmApp.Common.targets(875,5): error :
Failed to compile /home/jstur/projects/runtime/artifacts/bin/microsof
t.netcore.app.runtime.wasi-wasm/Debug/runtimes/wasi-wasm/native/src/p
invoke.c -> /home/jstur/projects/components/hello-wasm/obj/Debug/net9
.0/wasi-wasm/wasm/for-publish/pinvoke.o
In file included from /home/jstur/projects/runtime/artifacts/bin/micr
osoft.netcore.app.runtime.wasi-wasm/Debug/runtimes/wasi-wasm/native/s
rc/pinvoke.c:15:
/home/jstur/projects/components/hello-wasm/obj/Debug/net9.0/wasi-wasm
/wasm/for-publish/pinvoke-table.h:169:149: error: too few arguments t
o function call, expected 6, have 5
Is there a way to reference the runtime pack for testing outside of the repository? Maybe the approach in https://github.com/dotnet/runtime/blob/main/docs/workflow/testing/using-dev-shipping-packages.md is needed?
Running the samples provided in wasi folder in the repo work fine.
Reproduction Steps
I changed the approach a bit from what is documented in after finding other docs that suggested:
<Target Name="UpdateRuntimePack" AfterTargets="ResolveFrameworkReferences">
<ItemGroup>
<!-- update runtime pack to local build -->
<ResolvedRuntimePack
PackageDirectory="/home/jstur/projects/runtime/artifacts/bin/microsoft.netcore.app.runtime.wasi-wasm/Debug"
Condition="'%(ResolvedRuntimePack.FrameworkName)' == 'Microsoft.NETCore.App'" />
</ItemGroup>
</Target>
A sample repo is in: https://github.com/jsturtevant/test-runtime
Expected behavior
Should be able to test runtime with sample projects outside repo
Actual behavior
errors with linked code
Regression?
no
Known Workarounds
No response
Configuration
No response
Other information
No response
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·