Libdexterplugin Guidelines for Plugin Writers

Below are some guidelines for implementing plugins for Libdexter.

Use the provided dexterplugin.pc pkg-config file:
- for compile and link flags, e.g. pkg-config --cflags --libs dexterplugin.
- for the plugin library installation directory: pkg-config --variable=plugin_libdir dexterplugin.
- for your public header installation directory: pkg-config --variable=plugin_includedir dexterplugin.
Name your plugin libraries with a "dxt-" prefix, e.g. dxt-<yourplugin>.
Plugin shared libraries must not be versioned.
Plugins must export exactly three functions (and no more):
- dexter_plugin_init () - registers the plugin's services (types) with the GType system.
- dexter_plugin_exit () - performs any cleanup that may be required when the module unloads.
- dexter_plugin_get_services () - returns a DexterPluginServiceGroup describing all services that this plugin registers.
Each service implemented by the plugin must be a GObject derived from DexterPluginSampler
Each service implemented by the plugin must provide an implementation of the DexterPluginISampler interface.
If your plugin installs only one public header, i.e. it implements exactly one service, name it dxt-<yourplugin>-public.h and install it in the directory indicated by pkg-config --variable=plugin_includedir dexterplugin. For example:

                            /usr/include/
                               ./dexterpublic/
                                  ./dxt-yourplugin-public.h
If your plugin installs more than one header, i.e. it implements several services, create a sub-directory named dxt-<yourplugin> under the directory indicated by pkg-config --variable=plugin_includedir dexterplugin and install your headers there. For example:

                            /usr/include/
                               ./dexterpublic/
                                  ./dxt-yourplugin/
                                     ./service1-public.h
                                     ./service2-public.h