Hello,
I was assuming that something like that would be needed for the
dll/so, but the particular point I'm interested in is whether the main
app /has/ to be restarted, or if there are hacks that can get around
that.
which suggests that there are limits as to what can go into a dll/so.
In Delphi, it was possible to create components in a dynamic package,
store the packages in a plug-in directory, and have the application look
at the plug-in directory to load the various functions in the components.
Basically a dynamic package is just a dynamic library, with some
<intelligent> work to identify the components inside. The dynamic
loading of packages is not yet in FPC.
However, it is possible to emulate this behavior.
Look up the dynamic loading example here: http://www.tcoq.org/Lazarus.html
I've tested that some time ago for windows and it seems to work. I
haven't tested for Linux, though.
If you have any suggestions to improve that example, please send them ;-)
Best regards,
Thierry
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
