Skip to content

MagnumPlugins libraries have no lib prefix #144

Answered by mosra
Desperado17 asked this question in Q&A
Discussion options

You must be logged in to vote

That's intentional, these are all put to subdirectories based on the plugin interface and without a lib prefix, as they're meant to be loaded dynamically at runtime using the plugin manager.

Linking and using dynamic plugins directly as if they were shared libraries is not supported, if you don't want to perform dynamic loading at runtime, you can build the library and the plugins as static, but you'll lose quite a bit of flexibility that way, and the dependency libraries will be loaded in memory even though given plugin never gets actually …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Desperado17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants