lib/plugin/plugin.c: do not use G_MODULE_BIND_LOCAL for Python plugin provider
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Tue, 8 Aug 2017 20:37:42 +0000 (16:37 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Mon, 21 Aug 2017 21:02:22 +0000 (17:02 -0400)
commitb4fa1b59fab1ff8a0420844604314c777211a4ae
tree42bae3a6f1c2408a5d242c91a3eeb246e30e5370
parent361ac4a672191fd6a0642ace9724a393834f5634
lib/plugin/plugin.c: do not use G_MODULE_BIND_LOCAL for Python plugin provider

Using g_module_open() with the G_MODULE_BIND_LOCAL flag when loading the
Python plugin provider makes it impossible for _native_bt.so (the Python
module, part of the `bt2` package, generated by SWIG) to find libpython
symbols because the Python plugin provider is linked with libpython, not
_native_bt.so.

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
lib/plugin/plugin.c
This page took 0.026098 seconds and 4 git commands to generate.