Problem using LimeLM with TurboActivate

Thanks @reuk and @swar.
We found the solution.
It was caused by linking to the dynamic library using “@executable_path”.

As mentioned in that post (and just like you said, @swar):

it turns out that for plugins, “@executable_path” points to the Host’s binary.
To point to the plugin’s binary, we needed to use “@loader_path” instead.

So, using “@executable_path” for Standalone version and “@loader_path” for the Plugins, everything now works.