How to include 3rd party .dylib in plugin?

Development Pipeline & Plugins Plugins
, , , , ,
1

We have a plugin for which we are currently trying to add Mac support. The plugin contains a ThirdParty directory holding third party dynamic libraries for all platforms. As of 4.12, it is no longer possible to specify a path for a runtime dependency (see this post).

For Windows this is circumvented using PublicDelayLoadDLLs, but as far as I’m aware this does not exist on Mac.
On Mac, a project using our plugin fails to start the editor, due to not being able to find the third party dylib referenced by the plugin module. If we use the install_name_tool to specify a relative path to our ThirdParty folder, it works but then fails to work in a packaged build due to the different folder structure.

What is the process for distributing a plugin for Mac with third party library dependencies, without requiring users of the plugin to manually copy files around?

2

Bump. We have worked around this by using two copies of the dylib and running the install_name tool differently on each; we then select which to use in the build.cs file based on build configuration.

I would really like an official response on the right way of doing this though.

1 Like
3

Bump, is there an official way?