Make the Python plugin provider a libtool module
authorMichael Jeanson <mjeanson@efficios.com>
Wed, 10 Jul 2019 15:57:36 +0000 (11:57 -0400)
committerPhilippe Proulx <eeppeliteloop@gmail.com>
Thu, 11 Jul 2019 18:48:30 +0000 (14:48 -0400)
commitb14c7bf11ddef302870c4d1abf86d3a98f74cb08
tree52c6022adca8e6e7569daf77f162ab444528158f
parent2242b43d4f50ebdeabb124154fb8ac602c563536
Make the Python plugin provider a libtool module

The Python plugin provider is currently built as a library with an ABI
number and installed in the libdir. It is however not a library, it does
not provide a public API, no program should link to it and we load it
with g_module which is basically a wrapper over dlopen.

As such, build it as libtool "module" installed in the "plugin-providers"
subdirectory which is not part of the library search path.

Add an env variable 'LIBBABELTRACE2_PLUGIN_PROVIDER_DIR' that if is set
will override the builtin path to load the provider.

Change-Id: If475a89733c21f87d6a647e281326c13532a3d3d
Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/1682
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
Tested-by: jenkins <jenkins@lttng.org>
configure.ac
src/lib/Makefile.am
src/lib/plugin/Makefile.am
src/lib/plugin/plugin.c
src/python-plugin-provider/Makefile.am
tests/utils/utils.sh
This page took 0.025885 seconds and 4 git commands to generate.