-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] NativeLibrary
doesn't include file
#96864
Comments
For mono you need to use |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescriptionWith native-aot-llvm we are able to link a component type file by adding The object file is in reality an empty Wasm module that just contains two custom sections Related: #96419 @AaronRobinsonMSFT @lewing @yowl @jsturtevant Reproduction StepsAdd Expected behaviorFor the custom sections from the Actual behaviorDoes nothing. Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
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. |
@mkhamoyan to start this work we should add NativeLibrary items to the NativeFileReference items in the mono build. |
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>
andlinking
.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-exampleand 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
The text was updated successfully, but these errors were encountered: