Plugins and dynamic libraries

We’re currently using JUCE for standalone apps.

We’re now considering to release parts of some apps as plugins.
Our apps however make extensive use of shared libraries, both for third party code but also for our own code.

I read that plugins can also load shared libraries but I couldn’t really figure out if it was a good idea to do that or if it would be beneficial to use static linking instead.
Moving everything over to static libraries would be quite an endeavor so I’d prefer keeping the current approach but if using several shared libraries is more hassle then it may be worth switching to static in the long run.

From what I’ve experienced it is generally easier to use static linking, since there are many deployment issues like versioning that can be avoided.
However, if you’re aware of these issues and you’ve already figured out how to effectively ship and use dynamic libraries, I don’t see any reason why not to use this in plugins as well!

1 Like