[MichalStrehovsky]

Summary

Resolve the shared WASI SDK for NativeAOT runtime-test projects.

Import AcquireWasiSdk.targets for NativeAOT WASI tests and populate WASI_SDK_PATH before the NativeAOT OS-specific linker setup. Perform this in each test project because grouped test builds run in separate MSBuild processes and do not inherit properties computed by an outer target.

Also exclude WASM from the test infrastructure's Unix rpath linker argument.

Validation

On the combined local NativeAOT WASI bringup tree, including other unmerged enablement:

• .\src\tests\build.cmd nativeaot checked test nativeaot\SmokeTests\AttributeTrimming\AttributeTrimming.csproj wasm wasi passed, including after deleting the test artifacts.
• AttributeTrimming executed under Wasmtime with exit code 100.
• .\src\tests\build.cmd nativeaot checked tree nativeaot wasm wasi reached test compilation/linking; the latest run failed only on the existing UnitTests lowering assertion, with C math ABI warnings also remaining.

This branch contains only this cherry-picked commit from main; it was not built independently. Automated execution integration and Unix-host validation are not included.

Note

This PR description was generated by GitHub Copilot.

[dotnet-policy-service]

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

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib
See info in area-owners.md if you want to be subscribed.

[Copilot]

🔵 Needs a closer look

Reported validation depends on unmerged enablement, leaving standalone branch and Unix-host builds unverified.

No open issues 🎉

What changed in this PR

Resolves the shared WASI SDK within each NativeAOT runtime-test project, supporting grouped builds that use separate MSBuild processes.

Changes:

• Imports SDK acquisition and sets WASI_SDK_PATH before OS-specific linker setup.
• Excludes WASM targets from Unix rpath linker arguments.

File	Description
src/​tests/​Directory.Build.targets	Adds per-project WASI SDK resolution and excludes WASM from Unix rpath arguments.

_{Review effort: Balanced}

[MichalStrehovsky]

@dotnet/ilc-contrib could someone have a look? This is only doing a couple things:

• trigger AcquireWasiSdk.targets so that it sets up WASI build.
• Copy the value of RuntimeBuildWasiSdkPath (that the .targets set up and is a repo build convention) to WASI_SDK_PATH (that seems to be the product convention and Add dedicated NativeAOT WASM build integration for WASI #135955 set up native AOT targets to also use it)
• do not try setting rpath on WASI

[MichalStrehovsky]

Thanks!

[MichalStrehovsky]

/ba-g failure was #135963