GNOME Bugzilla – Bug 617140
Does not compile with -DGSEAL_ENABLE
Last modified: 2018-08-03 18:00:32 UTC
This module does not build with -DGSEAL_ENABLE. See http://live.gnome.org/GnomeGoals/UseGseal . Note that maybe this report cannot be fixed yet, as GTK+ still misses some accessor functions (see bug 588339, bug 597610) needed for sealing. Also see http://live.gnome.org/GTK%2B/3.0/PendingSealings for current status.
Created attachment 159836 [details] [review] Partial patch Partial patch fixing a few first issues. Bumps gtk+ requirement to 2.14. Feel free to commit if you're fine with it. For all the GtkAllocation fixing I'd prefer to have gtk 2.18. Can the requirement be bumped or to you prefer staying with 2.14 and using instead "#if GTK_CHECK_VERSION (2, x, y)" ?
ping - can this get a review?
Thanks for your contribution. The patch has been committed to the repository and will go into the next, 1.2.9 release. I've decided not to bump requirements for GTK+, just using instead `#if GTK_CHECK_VERSION(2,14,0)' where necessary
Reopening as it was a partial patch.
#if GTK_CHECK_VERSION stuff will make it extremely cumbersome. Adding a gtk-compat.h as other modules have done might be better.
Agreed, it's not ideal, but usually other modules use gtk-compat.h to define '#if GTK_CHECK_VERSION' and practically it's the same. In gcmd case, it's much simpler this way and it'll be far easier to identify obsoleted part of code when switching to gtk-3.0
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-commander/issues/44.