Chris Hamons

Error: ``` Xamarin.iOS 12.10.0.157 (d16-1): 6bd94753) using framework: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.2.sdk warning MT0136: Cannot find the assembly 'Xamarin.Essentials, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' referenced from '/Users/keith/Projects/bank-on-it-mobile/Source/Output/Debug/ObjC/netstandard2.0/BankOnIt.Game.ObjC.dll'. warning MT0136: Cannot find the assembly 'Xamarin.Essentials, Version=1.0.0.0,...

This is a reasonable feature request, but I'm not sure how much it buys you. From what I can tell the major benefit of modules here is include file handling,...

Similar / Duplicate of https://github.com/mono/Embeddinator-4000/issues/740 ?

This appears to be the general "we don't support things that don't match a pattern we've listed" error: https://github.com/mono/Embeddinator-4000/blob/master/objcgen/objcgenerator.cs#L1225

After doing some poking, I've verified this is the general "we only support limited return/param types" with classes with export. The HasClass \ HasProtocol check above is what we're failing....

I'm going to convert this issue into a "we should drastically improve the error message".

There is a XM sample that shows how to fire custom build steps: https://github.com/xamarin/mac-samples/blob/master/UseMSBuildToCopyFilesToBundleExample/UseMSBuildToCopyFilesToBundleExample/CustomBuildActions.targets But yes, we should have target people can pull in.

So @jbielski the Embeddinator-4000 doesn't actually use CppSharp under the hood. You can look at https://github.com/mono/Embeddinator-4000/blob/master/objcgen/objcgenerator.cs for example to see the ObjC code generator. It sounds like you would like...

I realized that my response was done with Apple colored glasses, I'm honestly not sure if the Android (Java/C) side uses CppSharp. @jonathanpeppers might know. Reopening

I think so based on this unit test - https://github.com/mono/Embeddinator-4000/blob/master/tests/managed/interfaces.cs