[wasi] Align build configuration with NativeAOT-LLVM

[maraf]

• [wasm] Integrate naot-llvm into workload manifest #101801 (Support PublishAOT=true)
• Allow to use emscripten workload separately emsdk#869
• [wasm] NativeLibrary doesn't include file #96864 (NativeFileReference vs NativeReference)
• Automatically compile .c native references

[SingleAccretion]

NativeAOT-LLVM as it currently is doesn't use PublishAot (in fact, it doesn't work with it). See dotnet/runtimelab#2235 (comment).

Is the first item here, effectively, about making it work?

[lewing]

NativeAOT-LLVM as it currently is doesn't use PublishAot (in fact, it doesn't work with it). See dotnet/runtimelab#2235 (comment).

Is the first item here, effectively, about making it work?

We definitely need an msbuild gesture to distinguish between the build targets, it seems like PublishAot is the correct one right now but your feedback is welcome.

[maraf]

The most problematic thing with PublishAot=true is that we need to know "current" version of LLVM packages.
One way to tackle the problem and minify changes needed in the client's proj, is to produce a custom/nuget SDK,

• It can disable mono workload
• It can update @(KnownILCompilerPack)
• So it could work with PublishAot=true
• The only thing needed would be add restore feed

EDIT: Current plan is to integrate needed bits directly into mono workload manifest

[pavelsavara]

why this is P0 ?

[maraf]

why this is P0 ?

Because lowering the barrier between two modes is important.