unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 6505@debbugs.gnu.org
Subject: bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in	preparation for Gtk+-3
Date: Fri, 25 Jun 2010 17:42:52 -0400	[thread overview]
Message-ID: <yxqtyoq94bn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4C24B408.5050703@swipnet.se> ("Jan Djärv"'s message of "Fri\, 25 Jun 2010 15\:50\:00 +0200")

Jan Djärv <jan.h.d@swipnet.se> writes:

> Dan Nicolaescu skrev 2010-06-24 20.34:
>>
>> Gtk+-3 will make some structure members private.
>>
>> Compiling with -DGSEAL_ENABLE points out the problems.
>>
>> See also http://live.gnome.org/GnomeGoals/UseGseal
>> for more info
>>
>>
>
> It is currently not an issue, configure checks for gtk+-2.0, so 3.0
> isn't considered yet.  Also, other libraries (rsvg, gconf possibly
> dbus) must also be moved forward.
>
> Apart from that, it is the question of how old Gtk+ we should
> support. Currently we say 2.6 (which is really old) or newer.  Most
> accessor functions in Gtk+ where introduced in 2.14, some in 2.16, and
> in one case, 2.20.
>
> We could add #ifdef:s, but I rather not do that unless we really need to.
>
> That said, I have a private branch that works with Gtk+ 3.0, and some
> of the fixes there can go in the trunk.  Maybe we should bump required
> to 2.14 and get most of the work checked in.

Good to hear you already have some solution.
IMHO the main thing is that emacs should not be seen as lagging
behind.  When the first distribution switches to version 3, it would be
good to have something available...





  parent reply	other threads:[~2010-06-25 21:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 18:34 bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3 Dan Nicolaescu
2010-06-25 13:50 ` Jan Djärv
2010-06-25 21:02   ` Glenn Morris
2010-06-25 22:47     ` Jan Djärv
2010-06-25 21:42   ` Dan Nicolaescu [this message]
2010-06-25 22:43     ` Jan Djärv
2010-06-27 17:56       ` Chong Yidong
2010-06-28  7:03         ` Yavor Doganov
2010-06-28 10:19           ` Jan Djärv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yxqtyoq94bn.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=6505@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).