Open MaxwellDAssistek opened 1 month ago
Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger See info in area-owners.md if you want to be subscribed.
.NET on Android uses the MonoVM runtime. R2R is only available with CoreCLR runtime and it's thus NOT available on Android.
However, MonoVM does support ahead of time compilation and profiled AOT.
@filipnavara I am looking to dynamically load some plugins during runtime, which prevents using AOT, so I was attempting to use Ready To Run to optimize the first-load performance of these plugins.
@filipnavara I am looking to dynamically load some plugins during runtime, which prevents using AOT, so I was attempting to use Ready To Run to optimize the first-load performance of these plugins.
MonoVM AOT is technically closer to how CoreCLR ReadyToRun works. It still allows dynamic code. It's NOT the same as NativeAOT that has the restrictions you are mentioning.
MonoVM AOT is technically closer to how CoreCLR ReadyToRun works. It still allows dynamic code. It's NOT the same as NativeAOT that has the restrictions you are mentioning.
I can't seem to find any clear instructions on how I can apply Mono AOT without Trimming being enforced.
Description
When I attempt to publish an Android project (with or without MAUI) using ReadyToRun, I get an exception while building.
Reproduction Steps
dotnet publish -f net8.0-android -c Release -p:RuntimeIdentifier=android-arm64
Expected behavior
Publish should complete successfully.
Actual behavior
Regression?
No response
Known Workarounds
No response
Configuration
.NET version 8.0.204 Windows 10
Other information
No response