Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
The default dllName for functions is "<library-name>". Since bindings for third party libraries will always be statically linked, "__Internal" would be a more useful default.
Good idea. I had "<library-name>" as my intention was to expand on this via clang modules to actually try to deduce the library, but that really is only useful for our product bindings internal to Xamarin.
"__Internal" makes much more sense as a default for third party bindings, at least on iOS. Definitely better than "<library-name>".
Keep in mind that the P/Invoke binding in general is nowhere near as correct or complete as the Objective-C binding is (for instance, ObjC object pointers need to actually be unsafe pointers or IntPtr in the extern signature). You are definitely expected to have to flesh it out, but I wanted to add rudimentary support for it. I will add a [Verify] category for P/Invoke as well.