Am Mon, 11 Aug 2014 15:36:18 +1200 schrieb Olly Betts <o...@survex.com>:
> 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). Hi there again, 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. I then tested with the dialogs sample from samples/dialogs/. Results: Binary compiled against generic-notification-wx also runs fine on libnotify-wx, though it shows the generic notifications still. A recompile yielded libnotify notifications. 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... Cheers, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
