Answers

• ChrisHamons USForum Administrator, Xamarin Team Xamurai

  September 2020

  https://docs.microsoft.com/en-us/xamarin/mac/platform/binding

  But yes, almost all of the documentation is iOS flavored. The process is pretty much identical.

  You can either use binding projects to bind obj-c libraries and native libraries and "raw" p/invokes to call C APIs.

  0
• VolodymyrSavchenko UAMember ✭✭✭

  September 2020 edited September 2020

  @ChrisHamons said:
  https://docs.microsoft.com/en-us/xamarin/mac/platform/binding

  But yes, almost all of the documentation is iOS flavored. The process is pretty much identical.

  You can either use binding projects to bind obj-c libraries and native libraries and "raw" p/invokes to call C APIs.

  Can you tell me please, what are the key differences in using binding project on iOS and macOS?

  0
• ChrisHamons USForum Administrator, Xamarin Team Xamurai

  September 2020

  Off the top of my head:

  • The input dylib/frameworks have different architecture slices. iOS almost always has multiple to cover simulator and device. macOS are often but not always x86_64 these days.
  • The process of creating a C# definition to map to the objc is the same, except the base types (UIKit vs AppKit classes)
  • The output (a managed dll with the lib embedded by default) is the same.
  • Use (include a reference in your app project) should be the same.

  0
• VolodymyrSavchenko UAMember ✭✭✭

  October 2020 Accepted Answer

  @ChrisHamons said:

  I don't know how, but it was enought to copy my .dylib files to my macOS project and then add native references to those files.
  That's all!

  0