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>
Fri, 11 Aug 2017 22:54:16 +0000 (18:54 -0400)
commitc92fb666a258aa91f1a5754cd6e32c96783cd80b
tree1f7c5cdd48121a788e919aa8ab793a1554cbb9ca
parent706a18f9d5d66f764b864085768dde24d342d308
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.024072 seconds and 4 git commands to generate.