If this is a problem, a preprocessor macro can be added to prevent that warning. GTK seems to use GTK_COMPILATION and and __GTK_H_INSIDE__ or something like that, which allow individual header inclusion.
They could also add another switch, e.g. BINDING_COMPILATION, so bindings can compile faster by including specific headers. Just an idea... or just include gtk.h everywhere, it's fine as long as the build takes reasonable time. On ה', 2014-02-27 at 12:26 +0100, Murray Cumming wrote: > On Wed, 2014-02-26 at 19:46 +0100, Juan Rafael García Blanco wrote: > > Hi, > > > > In the gtkmm documentation I’ve read that we should avoid including > > lib/lib.h, i.e. the main header file for the library we are wrapping, in > > .hg files. However I see this rule broken in gtk/src/enums.hg, where the > > whole gtk/gtk.h is included. Is this an exception? Or is there anything > > that I’m not taking into account? > > GTK+ changed their policy a few years ago. Now you often have no choice > but to include gtk.h. Trying to include an individual GTK+ header file > will generally cause a compiler error now. > > Murray > _______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
