static plugin vs dynamic plugin
-
Hi
Static plugin means its compiled into the exe and not loaded as
a shared LIB / DLL on demand.
Often a static linking is used if the plugin must always be
available in the app.
If the plugins features are more optional, dynamic can be used
so its loaded more like on demand. And can be optional. ( not installed)
However, with static linking, you must recompile the app if plugin changes.
With dynamic, you only need to recompile the plugin and the app would use the new
version. -
Hi
Static plugin means its compiled into the exe and not loaded as
a shared LIB / DLL on demand.
Often a static linking is used if the plugin must always be
available in the app.
If the plugins features are more optional, dynamic can be used
so its loaded more like on demand. And can be optional. ( not installed)
However, with static linking, you must recompile the app if plugin changes.
With dynamic, you only need to recompile the plugin and the app would use the new
version. -
Hi
Static plugin means its compiled into the exe and not loaded as
a shared LIB / DLL on demand.
Often a static linking is used if the plugin must always be
available in the app.
If the plugins features are more optional, dynamic can be used
so its loaded more like on demand. And can be optional. ( not installed)
However, with static linking, you must recompile the app if plugin changes.
With dynamic, you only need to recompile the plugin and the app would use the new
version. -
@mrjj is it mean if you want to use one plugin in multiple application you should use dynamic plugins it does not work on static plugins.
-
@hjohn It works in both cases.
The difference is: static plug-in is built into your executable (like a static lib) and dynamic plug-in is basically a shared library which is loaded at runtime. -
@jsulm yeah now its clear..one last question:In which specific case i should use static plugins?
-
