-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comments
I think the support was not fully there, because it was not possible to On Mon, Feb 2, 2015 at 2:53 AM, Masud Rahman notifications@github.com
|
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. |
Thanks! On Mon, Feb 2, 2015 at 12:52 PM, Masud Rahman notifications@github.com
|
It's possible that ce6613f fixes this issue. The tests would indicate so, but I have yet to actually build something with it! |
It is currently considered out of scope for |
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
orLoadLibrary
) 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.
The text was updated successfully, but these errors were encountered: