[wasm] NativeLibrary doesn't include file

[silesmo]

Description

With native-aot-llvm we are able to link a component type file by adding <NativeLibrary Include=\"{world_name}_component_type.o\" /> to the csproj file. With mono this doesn't do anything.

The object file is in reality an empty Wasm module that just contains two custom sections component-type:<WORLD_NAME> and linking.

Related: #96419

@AaronRobinsonMSFT @lewing @yowl @jsturtevant

Reproduction Steps

Add <NativeLibrary Include="numbers_component_type.o" />to Numbers.csproj in example: https://github.com/silesmo/wasm-unmanaged-callers-bug/tree/main/mono-example
and build.

Expected behavior

For the custom sections from the numbers_component_type.o to be included in the produced wasm file.

Actual behavior

Does nothing.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[radical]

For mono you need to use @(NativeFileReference).

[ghost]

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

Issue Details

---

Description

With native-aot-llvm we are able to link a component type file by adding <NativeLibrary Include=\"{world_name}_component_type.o\" /> to the csproj file. With mono this doesn't do anything.

The object file is in reality an empty Wasm module that just contains two custom sections component-type:<WORLD_NAME> and linking.

Related: #96419

@AaronRobinsonMSFT @lewing @yowl @jsturtevant

Reproduction Steps

Add <NativeLibrary Include="numbers_component_type.o" />to Numbers.csproj in example: https://github.com/silesmo/wasm-unmanaged-callers-bug/tree/main/mono-example
and build.

Expected behavior

For the custom sections from the numbers_component_type.o to be included in the produced wasm file.

Actual behavior

Does nothing.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author:	silesmo
Assignees:	-
Labels:	arch-wasm, untriaged, area-Build-mono
Milestone:	-

[lewing]

As @radical mentioned this is because the features coevolved. For .NET9 the plan is to resolve (as much as is practical) the differences in the build.

[lewing]

@mkhamoyan to start this work we should add NativeLibrary items to the NativeFileReference items in the mono build.