Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support plugins explicitly loaded at runtime #12

Closed
frutiger opened this issue Feb 2, 2015 · 6 comments
Closed

Support plugins explicitly loaded at runtime #12

frutiger opened this issue Feb 2, 2015 · 6 comments
Assignees

Comments

@frutiger
Copy link
Owner

frutiger commented Feb 2, 2015

A plugin explicitly loaded at runtime is a dynamically loadable module that exports some set of symbols. Other code may then load and use those symbols using operating system provided facilities (e.g. dlopen or LoadLibrary) if it knows the names and types of the exported symbols.

These dynamically loadable modules would have to be deployed together with the code using them in order to avoid mismatched symbol names and symbol signatures/behaviours.

This would implement option (1) from #7.

@frutiger
Copy link
Owner Author

frutiger commented Feb 2, 2015

I believe this is supported on the plugins branch (at 0a7237d). @cppguru, please let me know if that branch provides support for this kind of plugin, thanks!

@cppguru
Copy link

cppguru commented Feb 2, 2015

I think the support was not fully there, because it was not possible to
depend on what's inside a plugin without getting it into the link line. I
may remember wrong.

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

I believe this is supported on the plugins branch (at 0a7237d
0a7237d).
@cppguru https://github.com/cppguru, please let me know if that branch
provides support for this kind of plugin, thanks!


Reply to this email directly or view it on GitHub
#12 (comment).

@frutiger
Copy link
Owner Author

frutiger commented Feb 2, 2015

Ah yes, you are right, that support is still not there, however it should be relatively simple to add, I'll see what I can do.

@cppguru
Copy link

cppguru commented Feb 2, 2015

Thanks!

On Mon, Feb 2, 2015 at 12:52 PM, Masud Rahman notifications@github.com
wrote:

Ah yes, you are right, that support is still not there, however it should
be relatively simple to add, I'll see what I can do.


Reply to this email directly or view it on GitHub
#12 (comment).

@frutiger
Copy link
Owner Author

frutiger commented Feb 3, 2015

It's possible that ce6613f fixes this issue. The tests would indicate so, but I have yet to actually build something with it!

@frutiger
Copy link
Owner Author

frutiger commented Sep 2, 2018

It is currently considered out of scope for bdemeta to support understanding dependencies between libraries at runtime. Note that code may load a dependency at runtime as usual, there is no magic provided by the build system to automatically switch between a library loaded at runtime vs. linked against at link time.

@frutiger frutiger closed this as completed Sep 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants