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

Olly Betts olly at survex.com
Mon Aug 11 03:36:18 UTC 2014

I've just been looking into this in more detail - unfortunately,
enabling this option looks like it may be an ABI-incompatible change.

In include/wx/notifmsg.h we have:

if defined(__WXGTK__) && wxUSE_LIBNOTIFY
    #include "wx/gtk/notifmsg.h"
#elif defined(__WXGTK__) && (wxUSE_LIBHILDON || wxUSE_LIBHILDON2)
    #include "wx/gtk/hildon/notifmsg.h"
    #include "wx/msw/notifmsg.h"
    #include "wx/generic/notifmsg.h"
    class wxNotificationMessage : public wxGenericNotificationMessage
        wxNotificationMessage() { }
        wxNotificationMessage(const wxString& title,
                              const wxString& message = wxEmptyString,
                              wxWindow *parent = NULL,
                              int flags = wxICON_INFORMATION)
            : wxGenericNotificationMessage(title, message, parent, flags)

And looking in include/wx/gtk/notifmsg.h, there's a different version of
class wxNotificationMessage in that case.

I've not yet tried a build to see if this is an ABI break, or it's
actually all OK (wx uses symbol visibility and the wxNotificationMessage
definition above for the generic case is all inline, so there's still
some hope).

But if this change is ABI incompatible, that probably means this is
unfeasible to do before jessie, as it'd require binnmus for the ~90
packages which build-depend on wxwidgets, and I'm already too busy
trying to push through the transitions to wxwidgets3.0 and wxpython3.0.


More information about the Freewx-maint mailing list