-
Notifications
You must be signed in to change notification settings - Fork 1.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
Request for disambiguation of NativeReference and ObjCBindingLibrary #21352
Comments
I think you want the SDK repo, this is for the MAUI UI project and doesn't maintain that tooling. CC @rolfbjarne |
The recommendation is to never use |
Could we mark Funnily enough, i was binding a library using |
Yes, we could issue a warning if |
This issue was moved to xamarin/xamarin-macios#20358 |
Hello .NET MAUI devs,
like many other devs i am migrating to .NET 8. I am working with a few native SDKs for Android and iOS respectively and i ran into a few binding problems which are close to be fixed.
During my ordeal i made what turned out to be a mistake and tried to bind every SDK using
ObjCBindingNativeLibrary
, thus introducing a build error involving clang++. I tried to bind some SDKs usingObjCBindingNativeLibrary
and others usingNativeReference
and while i could push the build errors aside, i could not actually use the SDK i bound usingObjCBindingNativeLibrary
during runtime.Now i've bound every SDK again using
NativeReference
and while i'm still dealing with build errors (duplicate symbols, a potential regression in my specific case compared to Xamarin.iOS) i would like to know the following:What is the difference between
NativeReference
andObjCBindingNativeLibrary
If i had to guess it's that
ObjCBindingNativeLibrary
is some internal thing. I've seen a few people use in the Github Issues but none of the devs have actively discouraged the use of it AFAIK. I do know however thatNativeReference
works better with the SDKs and that Microsoft asks devs to use that to reference SDKs in .NET 8.The text was updated successfully, but these errors were encountered: