* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
@ 2010-06-24 18:34 Dan Nicolaescu
2010-06-25 13:50 ` Jan Djärv
0 siblings, 1 reply; 9+ messages in thread
From: Dan Nicolaescu @ 2010-06-24 18:34 UTC (permalink / raw)
To: 6505
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
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 21:42 ` Dan Nicolaescu
0 siblings, 2 replies; 9+ messages in thread
From: Jan Djärv @ 2010-06-25 13:50 UTC (permalink / raw)
Cc: 6505
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.
Jan D.
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
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
1 sibling, 1 reply; 9+ messages in thread
From: Glenn Morris @ 2010-06-25 21:02 UTC (permalink / raw)
To: Jan Djärv; +Cc: 6505
Jan Djärv wrote:
> 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.
For the record, RHEL 5, the most recent Red Hat Enterprise Linux, only
has 2.10. I don't have an opinion whether that is important or not.
There will probably be a RHEL 6 (with 2.18) before Emacs 24.1.
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
2010-06-25 21:02 ` Glenn Morris
@ 2010-06-25 22:47 ` Jan Djärv
0 siblings, 0 replies; 9+ messages in thread
From: Jan Djärv @ 2010-06-25 22:47 UTC (permalink / raw)
To: Glenn Morris; +Cc: 6505@debbugs.gnu.org
25 jun 2010 kl. 23:02 skrev Glenn Morris <rgm@gnu.org>:
> Jan Djärv wrote:
>
>> 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.
>
> For the record, RHEL 5, the most recent Red Hat Enterprise Linux, only
> has 2.10. I don't have an opinion whether that is important or not.
> There will probably be a RHEL 6 (with 2.18) before Emacs 24.1.
Good to know. Thanks.
Jan D.
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
2010-06-25 13:50 ` Jan Djärv
2010-06-25 21:02 ` Glenn Morris
@ 2010-06-25 21:42 ` Dan Nicolaescu
2010-06-25 22:43 ` Jan Djärv
1 sibling, 1 reply; 9+ messages in thread
From: Dan Nicolaescu @ 2010-06-25 21:42 UTC (permalink / raw)
To: Jan Djärv; +Cc: 6505
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...
^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
2010-06-25 21:42 ` Dan Nicolaescu
@ 2010-06-25 22:43 ` Jan Djärv
2010-06-27 17:56 ` Chong Yidong
0 siblings, 1 reply; 9+ messages in thread
From: Jan Djärv @ 2010-06-25 22:43 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: 6505@debbugs.gnu.org
25 jun 2010 kl. 23:42 skrev Dan Nicolaescu <dann@gnu.org>:
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
> 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...
I
we must see a Gnome based on Gtk 3.0 first. It is not possible (without #ifdefs) to support < 2.14 and 3.0.
If it is just a few ifdefs I will add them. But we need to decide if configure should start to check for Gtk 3.0. Maybe now is the time.
Jan D.
^ permalink raw reply [flat|nested] 9+ messages in thread* bug#6505: make the Gtk+ port compile with -DGSEAL_ENABLE in preparation for Gtk+-3
2010-06-25 22:43 ` Jan Djärv
@ 2010-06-27 17:56 ` Chong Yidong
2010-06-28 7:03 ` Yavor Doganov
0 siblings, 1 reply; 9+ messages in thread
From: Chong Yidong @ 2010-06-27 17:56 UTC (permalink / raw)
To: Jan Djärv; +Cc: Dan Nicolaescu, 6505@debbugs.gnu.org
Jan Djärv <jan.h.d@swipnet.se> writes:
> 25 jun 2010 kl. 23:42 skrev Dan Nicolaescu <dann@gnu.org>:
>
>> 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...
>
> I we must see a Gnome based on Gtk 3.0 first. It is not possible
> (without #ifdefs) to support < 2.14 and 3.0.
>
> If it is just a few ifdefs I will add them. But we need to decide if
> configure should start to check for Gtk 3.0. Maybe now is the time.
Yes, I think bumping the requirement to 2.14 in the trunk is fine, as is
adding support for 3.0, provided it does not interfere with the GTK-2
support. Thanks for working ahead on this.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2010-06-28 10:19 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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).