-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Closed
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-Build-monoin-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged
Milestone
Description
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
Metadata
Metadata
Assignees
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-Build-monoin-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged