Support plugins automatically loaded at runtime

[frutiger]

A plugin automatically loaded at runtime is a shared library that is provided as a link-time dependency of some other code. This other code may then freely use symbols from the plugin as long the name of the exported symbols are known (e.g. through header files).

These shared libraries would have to be deployed together with the code using them in order to avoid mismatched symbol names and symbol signatures/behaviours. This stands in contrast to #14 where the resulting binary contains all the requisite dependencies.

This would implement option (2) from #7.

[cppguru]

It is a "third" other code that can run the functions. Remember, the
"other code" has no kind of dep on the code loaded. That "3rd code" must
have a way of depending on the loaded module (if that is not just a
standardized script module) to include headers without creating link time
dependencies.

On Mon, Feb 2, 2015 at 2:38 AM, Masud Rahman notifications@github.com
wrote:

A plugin automatically loaded at runtime is a shared library that is
provided as a link-time dependency of some other code. This other code may
then freely use functions from the library without any special code or
management.

This would implement option (2) from #7
#7.

—
Reply to this email directly or view it on GitHub
#13.

[frutiger]

This can be handled the same way as the issue resolution for #14.