mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-01-12 15:36:17 +01:00
Improve the documentation about single include exceptions
Also, reenable the compiling Glib application section Fixes https://bugzilla.gnome.org/show_bug.cgi?id=612736
This commit is contained in:
parent
5b19345246
commit
62a133f55d
@ -75,6 +75,15 @@ by using the command line option <literal>-DG_DISABLE_DEPRECATED=1</literal>.
|
||||
The recommended way of using GLib has always been to only include the
|
||||
toplevel headers <filename>glib.h</filename>,
|
||||
<filename>glib-object.h</filename>, <filename>gio.h</filename>.
|
||||
Still, there are some exceptions; these headers have to be included separately:
|
||||
<filename>gmodule.h</filename>,
|
||||
<filename>glib/gi18n-lib.h</filename> or <filename>glib/gi18n.h</filename> (see
|
||||
the <link linkend="glib-I18N">Internationalization section</link>),
|
||||
<filename>glib/gprintf.h</filename> and <filename>glib/gstdio.h</filename>
|
||||
(we don't want to pull in all of stdio).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Starting with 2.17, GLib enforces this by generating an error
|
||||
when individual headers are directly included. To help with the
|
||||
transition, the enforcement is not turned on by default for GLib
|
||||
|
@ -32,6 +32,7 @@ synchronize their operation.
|
||||
|
||||
<xi:include href="building.sgml" />
|
||||
<xi:include href="cross.sgml" />
|
||||
<xi:include href="compiling.sgml" />
|
||||
<xi:include href="running.sgml" />
|
||||
<xi:include href="changes.sgml" />
|
||||
<xi:include href="regex-syntax.sgml" />
|
||||
|
Loading…
Reference in New Issue
Block a user