[Freewx-maint] Bug#745887: libwxgtk3.0-0: Please enable support for libnotify

Olly Betts olly at survex.com
Tue Sep 9 17:31:34 UTC 2014


On Tue, Sep 09, 2014 at 07:17:53PM +0200, Christian Beier wrote:
> I've built two versions of the library, one with libnotify support and one
> without. Turns out that --with-libnotify is enabled by default and only
> libnotify-dev needs to be added to the build-deps to get libnotify
> notifications. The abi-compliance-checker tool
> (http://ispras.linuxbase.org/index.php/ABI_compliance_checker) reported no
> problems between the two versions, fine so far. 

Can you show the report from checking with the inputs switched?  I.e.
the result of "upgrading" from using libnotify to not.  That should
show us all the symbols which get added by turning on libnotify, which
would be useful to know.

> Other way round it doesn't work: the dialogs binary built against
> libnotify-wx does not run with generic-notification-wx, I get a
>  
>  ./dialogs: relocation error: ./dialogs: symbol _ZTV21wxNotificationMessage,
>  version WXU_3.0 not defined in file libwx_gtk2u_adv-3.0.so.0 with link time
>  reference
> 
> which is acceptable since we're moving the other direction...

That does sound promising.

We just need to make sure packages compiled against the newer library
will get a suitable >= dependency, which I think we can with a suitable
shlibs file, though I've never tried to do so before.

Thanks for looking into this - if it's actually possible to do, I'll
try to ensure it gets in before the freeze.

Cheers,
    Olly



More information about the Freewx-maint mailing list