> On Dec 1, 2016, at 7:58 AM, Andreas Falkenhahn <andr...@falkenhahn.com> wrote:
> My app supports external plugins. On macOS, Linux, and Windows those plugins
> are just shared objects/dylibs (or DLLs) loaded via dlopen() (or LoadLibrary()
> on Windows) at runtime.
Does iOS still not support dlopen? I thought that, when iOS 8 granted the
ability to load dynamic libraries, that dlopen would start working.
What about the CFBundle API? Is that supported?
> Now I'm looking for a way to port this design to iOS. The obvious choice seems
> to be turning the individual plugins into individual Cocoa Touch Frameworks.
> However, this results in the following big problem: The symbol names are the
> same for every plugin, i.e. every plugin has a symbol named InitPlugin(), a
> symbol named FreePlugin(), and so on.
If you use frameworks then yes, you’ll have to rename the exported symbols in
every plugin to be unique.
Cocoa-dev mailing list (Cocoaemail@example.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to arch...@mail-archive.com