ANNOUNCE: Xffm release

[Marcel Pol]

Edscott Wilson Garcia wrote:
> Xffm-4.3.2.1 is now released. 

I have an issue with the plugins. They are called plugins, and according
to the lib.la files xffm uses dlopen for them. I'd think that if they
are plugins, they don't need a SONAME, and xffm could just dlopen the
lib.so file.
Afaik a SONAME is only used for real libraries.

What happens is something different though. When xffm is run without the
lib.so files installed it gives this error:

$ xffm
** (xffm:23469): WARNING **: Cannot connect to session manager
** (xffm:23469): WARNING **: g_module_open(/usr/lib/libxffm_icons.so) ==
NULL
** (xffm:23469): WARNING **: Module cannot be opened! Check if correctly
installed...
** (xffm:23469): WARNING **: Show stopper: cannot get module info for
xffm_icons
xffm: signal 11 received. Cleaning up before exiting
xffm: logfile = /home/marcel/.cache/xfce4/xffm/xffm_error.log
xffm: dumping core at= /home/marcel/.cache/xfce4/xffm
Aborted
$

I'm no programmer, so I don't know if g_module_open is being used for
plugins or libraries, but it is trying to open a lib.so file, which is
or a plugin, or it is a development library. That confuses me a bit,
what is it? If it would be a real plugin, xffm shouldn't break on it not
being present. If it's a library, it should open the versioned lib.so.2.
So my question is, should I treat these files as plugins or libraries?


For reference, I listed the SONAME's below:
$ objdump -x libxffm_actions.so libxffm_basic.so \
libxffm_calls.so libxffm_cpy.so libxffm_primary.so \
libxffm_secondary.so libxffm_tubo.so |grep SO
  SONAME      libxffm_actions.so.2
  SONAME      libxffm_basic.so.2
  SONAME      libxffm_calls.so.2
  SONAME      libxffm_cpy.so.2
  SONAME      libxffm_primary.so.2
  SONAME      libxffm_secondary.so.2
  SONAME      libxffm_tubo.so.2

Regards,
Marcel Pol