On Thu, Mar 10, 2016 at 10:12 AM, Nicolas Danet nicolas.danet@free.fr wrote:
Does it means that if the host opens the plug-in with RTLD_LOCAL flag, that plug-in will not be able to export its symbols table to its own dlopened externals (even doing it with RTLD_GLOBAL)?
It's been a while since I worked with this, but I think that's correct. You have to load the pure data code with RTLD_GLOBAL in order to load pd externals. And as I said, you can do that from your plugin just be creating another dynamic library which is loaded from your plugin.
Yes, I think you're right. The DAW may load the plugins with RTLD_LOCAL that's why my symbols are not accessible. Thanks a lot ! So I have to load dynamic libraries in Pure Data that is already a dynamic library loaded by my plugin that is already a dynamic library loaded by the DAW... it sounds like Inception.
2016-03-10 10:19 GMT+01:00 Kjetil Matheussen k.s.matheussen@gmail.com:
On Thu, Mar 10, 2016 at 10:12 AM, Nicolas Danet nicolas.danet@free.fr wrote:
Does it means that if the host opens the plug-in with RTLD_LOCAL flag, that plug-in will not be able to export its symbols table to its own dlopened externals (even doing it with RTLD_GLOBAL)?
It's been a while since I worked with this, but I think that's correct. You have to load the pure data code with RTLD_GLOBAL in order to load pd externals. And as I said, you can do that from your plugin just be creating another dynamic library which is loaded from your plugin.
Pd-dev mailing list Pd-dev@lists.iem.at http://lists.puredata.info/listinfo/pd-dev
-
Kjetil Matheussen -
Pierre Guillot