-
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
[NativeAOT] Low level API support for Objective-C scenarios #77472
Comments
Yes, we are happy to merge contributions that fill in missing functionality in NativeAOT.
These CoreCLR hosting APIs do not make a lot of sense in NativeAOT world. The basic NativeAOT hosting primitive is |
Yes, that's fine. Smaller PRs are typically reviewed and merged faster that makes it easier to make progress. |
/cc @ivanpovazan |
I agree that the full set of CoreCLR hosting APIs does not make sense for NativeAOT. The only feature that Xamarin-macios needs from a "hosting" API is the ability to call |
@AustinWise Marking this as future since there is no rush and no expectation all of it will be done in .NET 8. If you are able to make it happen hooray, just don't want to put undue pressure on you. |
@AaronRobinsonMSFT This API is now implemented to a sufficient degree to unblock #80905. The milestone can be updated to .NET 8. One small piece of the API in unimplemented. Since Xamarin does not currently use it, I have separated it out to its own tracking ticket: #80985 |
.NET 6 added some APIs to CoreCLR to support running the macOS version of Xamarin-macios. Reference:
High level questions about how to approach implementing this
ObjectiveCMarshal
API be split over multiple PRs. If so, is there a recommended way to turn off the feature for release builds, but still have the CI system test the feature?Outline of work
ObjectiveCMarshal
API :Unimplemented parts of the API
Since the Xamarin side does not use the
lastMethod
parameter of theUnhandledExceptionPropagationHandler
delegate, implmenting that is tracked in a separate issue: #80985The text was updated successfully, but these errors were encountered: