After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 563636 - Use single GTK includes
Use single GTK includes
Status: RESOLVED WONTFIX
Product: xchat-gnome
Classification: Other
Component: general
HEAD
Other Linux
: Normal normal
: ---
Assigned To: xchat-gnome maintainers
xchat-gnome maintainers
gnome[unmaintained]
Depends on: 564615 586222
Blocks:
 
 
Reported: 2008-12-08 05:15 UTC by Pedro Fragoso
Modified: 2019-02-23 02:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use single includes (8.05 KB, patch)
2008-12-08 05:16 UTC, Pedro Fragoso
none Details | Review
xchat-gnome fixed patch (5.66 KB, patch)
2008-12-15 14:29 UTC, Przemysław Grzegorczyk
committed Details | Review

Comment 1 Pedro Fragoso 2008-12-08 05:16:46 UTC
Created attachment 124142 [details] [review]
Use single includes
Comment 2 Christian Persch 2008-12-08 11:51:42 UTC
Thanks! Please commit to trunk.
Comment 3 Pedro Fragoso 2008-12-08 13:38:31 UTC
Thanks chpe, but i don't have a svn access. Someone feel free to commit this.
Comment 4 Przemysław Grzegorczyk 2008-12-15 14:29:20 UTC
Created attachment 124730 [details] [review]
xchat-gnome fixed patch

This patch is a fixed version of Pedro's patch.
gdkkeysyms.h is not included in gdk.h so can't be replaced by gdk.h.

To compile xchat-gnome with single includes flags libsexy need to be fixed (bug 564615).
Comment 5 Christian Persch 2009-01-16 13:25:13 UTC
Committed, thanks for the patches!
Comment 6 Javier Jardón (IRC: jjardon) 2009-05-05 20:09:39 UTC
I can't compile with -DGTK_DISABLE_SINGLE_INCLUDES

Maybe because bug #564615 is not fixed ?
Comment 7 C de-Avillez 2009-05-05 21:36:26 UTC
reopening, based on chat in #bugs. User will add more data.
Comment 8 Javier Jardón (IRC: jjardon) 2009-05-05 21:37:30 UTC
I download xchat from gnome git repository today (2009/05/05)
Comment 9 Javier Jardón (IRC: jjardon) 2009-05-05 21:42:20 UTC
This is the error:

"
In file included from /usr/include/libsexy/sexy-spell-entry.h:28,
                 from text-entry.h:24,
                 from fe-gnome.c:40:
/usr/include/gtk-2.0/gtk/gtkentry.h:32:2: error: #error "Only <gtk/gtk.h> can be included directly."
make[4]: *** [xchat_gnome-fe-gnome.o] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
"
Comment 10 Christian Persch 2009-05-05 21:47:23 UTC
That's a bug in libsexy then, which I thought was fixed already (bug 564615).
Comment 11 Ritesh Khadgaray ( irc:ritz) 2009-06-18 09:12:36 UTC
note: http://live.gnome.org/GnomeGoals/DropLibsexy
Comment 12 Ritesh Khadgaray ( irc:ritz) 2009-11-18 15:51:44 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 13 Ritesh Khadgaray ( irc:ritz) 2009-11-18 16:14:58 UTC
correction, issue lies with libsexy and not xchat-gnome.
Comment 14 Ritesh Khadgaray ( irc:ritz) 2009-11-18 16:34:58 UTC
Two items remains here 

1. libsexy - to be dropped, once we have a replacement for  SexySpellEntry.
Workaround, manually edit "libsexy/sexy-spell-entry.h", to use "<gtk/gtk.h>"

2. gdk/gdkkeysyms.h
awaiting feedback on  http://live.gnome.org/GnomeGoals/CleanupGTKIncludes
Comment 15 André Klapper 2010-06-28 15:11:51 UTC
Not done as comment 14 point 1. Reopening and adding dependency.
Comment 16 André Klapper 2019-02-23 02:48:44 UTC
xchat-gnome is not under active development anymore.
Its codebase has been archived:
https://gitlab.gnome.org/Archive/xchat-gnome/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather reactivate the project
to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the
responsibility for active development again.
You may want to switch to Hexchat (or another IRC client that suits you).