RubyGems - glib2 - Versions diffs - 3.2.1-x86-mingw32 → 3.2.2-x86-mingw32 - Mend

glib2 3.2.1-x86-mingw32 → 3.2.2-x86-mingw32

Files changed (927) hide show

data/vendor/local/share/gtk-doc/html/glib/glib-Version-Information.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib-fundamentals.html" title="GLib Fundamentals">
 <link rel="prev" href="glib-fundamentals.html" title="GLib Fundamentals">
 <link rel="next" href="glib-Basic-Types.html" title="Basic Types">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -149,6 +149,18 @@
 </tr>
 <tr>
 <td class="define_keyword">#define</td>
+<td class="function_name"><a class="link" href="glib-Version-Information.html#GLIB-VERSION-2-52:CAPS" title="GLIB_VERSION_2_52">GLIB_VERSION_2_52</a></td>
+</tr>
+<tr>
+<td class="define_keyword">#define</td>
+<td class="function_name"><a class="link" href="glib-Version-Information.html#GLIB-VERSION-2-54:CAPS" title="GLIB_VERSION_2_54">GLIB_VERSION_2_54</a></td>
+</tr>
+<tr>
+<td class="define_keyword">#define</td>
+<td class="function_name"><a class="link" href="glib-Version-Information.html#GLIB-VERSION-2-56:CAPS" title="GLIB_VERSION_2_56">GLIB_VERSION_2_56</a></td>
+</tr>
+<tr>
+<td class="define_keyword">#define</td>
 <td class="function_name"><a class="link" href="glib-Version-Information.html#GLIB-VERSION-MIN-REQUIRED:CAPS" title="GLIB_VERSION_MIN_REQUIRED">GLIB_VERSION_MIN_REQUIRED</a></td>
 </tr>
 <tr>
@@ -345,7 +357,7 @@ linked against at application run time.</p>
 <hr>
 <div class="refsect2">
 <a name="GLIB-MINOR-VERSION:CAPS"></a><h3>GLIB_MINOR_VERSION</h3>
-<pre class="programlisting">#define GLIB_MINOR_VERSION 54
+<pre class="programlisting">#define GLIB_MINOR_VERSION 56
 </pre>
 <p>The minor version number of the GLib library.</p>
 <p>Like <span class="type">gtk_minor_version</span>, but from the headers used at
@@ -355,7 +367,7 @@ linked against at application run time.</p>
 <hr>
 <div class="refsect2">
 <a name="GLIB-MICRO-VERSION:CAPS"></a><h3>GLIB_MICRO_VERSION</h3>
-<pre class="programlisting">#define GLIB_MICRO_VERSION 1
+<pre class="programlisting">#define GLIB_MICRO_VERSION 0
 </pre>
 <p>The micro version number of the GLib library.</p>
 <p>Like <span class="type">gtk_micro_version</span>, but from the headers used at
@@ -481,6 +493,33 @@ that can be used by the C pre-processor.</p>
 </div>
 <hr>
 <div class="refsect2">
+<a name="GLIB-VERSION-2-52:CAPS"></a><h3>GLIB_VERSION_2_52</h3>
+<pre class="programlisting">#define GLIB_VERSION_2_52       (G_ENCODE_VERSION (2, 52))
+</pre>
+<p>A macro that evaluates to the 2.52 version of GLib, in a format
+that can be used by the C pre-processor.</p>
+<p class="since">Since: <a class="link" href="api-index-2-52.html#api-index-2.52">2.52</a></p>
+</div>
+<hr>
+<div class="refsect2">
+<a name="GLIB-VERSION-2-54:CAPS"></a><h3>GLIB_VERSION_2_54</h3>
+<pre class="programlisting">#define GLIB_VERSION_2_54       (G_ENCODE_VERSION (2, 54))
+</pre>
+<p>A macro that evaluates to the 2.54 version of GLib, in a format
+that can be used by the C pre-processor.</p>
+<p class="since">Since: <a class="link" href="api-index-2-54.html#api-index-2.54">2.54</a></p>
+</div>
+<hr>
+<div class="refsect2">
+<a name="GLIB-VERSION-2-56:CAPS"></a><h3>GLIB_VERSION_2_56</h3>
+<pre class="programlisting">#define GLIB_VERSION_2_56       (G_ENCODE_VERSION (2, 56))
+</pre>
+<p>A macro that evaluates to the 2.56 version of GLib, in a format
+that can be used by the C pre-processor.</p>
+<p class="since">Since: <a class="link" href="api-index-2-56.html#api-index-2.56">2.56</a></p>
+</div>
+<hr>
+<div class="refsect2">
 <a name="GLIB-VERSION-MIN-REQUIRED:CAPS"></a><h3>GLIB_VERSION_MIN_REQUIRED</h3>
 <pre class="programlisting"># define GLIB_VERSION_MIN_REQUIRED      (GLIB_VERSION_CUR_STABLE)
 </pre>
@@ -527,6 +566,6 @@ of deprecated GLib APIs.</p>
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-Warnings-and-Assertions.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib-core.html" title="GLib Core Application Support">
 <link rel="prev" href="glib-Error-Reporting.html" title="Error Reporting">
 <link rel="next" href="glib-Message-Logging.html" title="Message Output and Debugging Functions">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -321,9 +321,26 @@ function, so that it avoids this incorrect call.</p>
  evaluates to <a class="link" href="glib-Standard-Macros.html#FALSE:CAPS" title="FALSE"><code class="literal">FALSE</code></a>,
 the result is usually that a critical message is logged and the current
 function returns.</p>
-<p>If G_DISABLE_CHECKS is defined then the check is not performed.  You
+<p>If <code class="literal">G_DISABLE_CHECKS</code> is defined then the check is not performed.  You
 should therefore not depend on any side effects of <em class="parameter"><code>expr</code></em>
 .</p>
+<p>To debug failure of a <a class="link" href="glib-Warnings-and-Assertions.html#g-return-if-fail" title="g_return_if_fail()"><code class="function">g_return_if_fail()</code></a> check, run the code under a debugger
+with <code class="literal">G_DEBUG=fatal-criticals</code> or <code class="literal">G_DEBUG=fatal-warnings</code> defined in the
+environment (see <a class="ulink" href="glib-running.html" target="_top">Running GLib Applications</a>):</p>
+<div class="informalexample">
+  <table class="listing_frame" border="0" cellpadding="0" cellspacing="0">
+    <tbody>
+      <tr>
+        <td class="listing_lines" align="right"><pre>1</pre></td>
+        <td class="listing_code"><pre class="programlisting"><span class="normal">G_DEBUG</span><span class="symbol">=</span><span class="normal">fatal</span><span class="symbol">-</span><span class="usertype">warnings</span><span class="normal"> gdb </span><span class="symbol">./</span><span class="normal">my</span><span class="symbol">-</span><span class="normal">program</span></pre></td>
+      </tr>
+    </tbody>
+  </table>
+</div>
+<p></p>
+<p>Any unrelated failures can be skipped over in
+<a class="ulink" href="https://www.gnu.org/software/gdb/" target="_top">gdb</a> using the <code class="literal">continue</code> command.</p>
 <div class="refsect3">
 <a name="g-return-if-fail.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -358,9 +375,10 @@ function, so that it avoids this incorrect call.</p>
 the result is usually that a critical message is logged and <em class="parameter"><code>val</code></em>
  is
 returned from the current function.</p>
-<p>If G_DISABLE_CHECKS is defined then the check is not performed.  You
+<p>If <code class="literal">G_DISABLE_CHECKS</code> is defined then the check is not performed.  You
 should therefore not depend on any side effects of <em class="parameter"><code>expr</code></em>
 .</p>
+<p>See <a class="link" href="glib-Warnings-and-Assertions.html#g-return-if-fail" title="g_return_if_fail()"><code class="function">g_return_if_fail()</code></a> for guidance on how to debug failure of this check.</p>
 <div class="refsect3">
 <a name="g-return-val-if-fail.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -391,6 +409,7 @@ if the expression is not true</p></td>
 <pre class="programlisting">#define             g_return_if_reached()</pre>
 <p>Logs a critical message and returns from the current function.
 This can only be used in functions which do not return a value.</p>
+<p>See <a class="link" href="glib-Warnings-and-Assertions.html#g-return-if-fail" title="g_return_if_fail()"><code class="function">g_return_if_fail()</code></a> for guidance on how to debug failure of this check.</p>
 </div>
 <hr>
 <div class="refsect2">
@@ -398,6 +417,7 @@ This can only be used in functions which do not return a value.</p>
 <pre class="programlisting">#define             g_return_val_if_reached(val)</pre>
 <p>Logs a critical message and returns <em class="parameter"><code>val</code></em>
 .</p>
+<p>See <a class="link" href="glib-Warnings-and-Assertions.html#g-return-if-fail" title="g_return_if_fail()"><code class="function">g_return_if_fail()</code></a> for guidance on how to debug failure of this check.</p>
 <div class="refsect3">
 <a name="g-return-val-if-reached.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -480,29 +500,29 @@ the <a class="link" href="glib-Message-Logging.html#g-log" title="g_log ()"><co
 21
 22
 23</pre></td>
-        <td class="listing_code"><pre class="programlisting"><span class="gtkdoc ppc">#include &lt;glib.h&gt;</span>
+        <td class="listing_code"><pre class="programlisting"><span class="preproc">#include</span><span class="normal"> </span><span class="string">&lt;glib.h&gt;</span>
-<span class="gtkdoc kwb">static void</span>
-<span class="function">log_handler</span> <span class="gtkdoc opt">(</span><span class="gtkdoc kwb">const</span> gchar   <span class="gtkdoc opt">*</span>log_domain<span class="gtkdoc opt">,</span>
-             GLogLevelFlags log_level<span class="gtkdoc opt">,</span>
-             <span class="gtkdoc kwb">const</span> gchar   <span class="gtkdoc opt">*</span>message<span class="gtkdoc opt">,</span>
-             gpointer       user_data<span class="gtkdoc opt">)</span>
-<span class="gtkdoc opt">{</span>
-  <span class="function"><a href="glib-Message-Logging.html#g-log-default-handler">g_log_default_handler</a></span> <span class="gtkdoc opt">(</span>log_domain<span class="gtkdoc opt">,</span> log_level<span class="gtkdoc opt">,</span> message<span class="gtkdoc opt">,</span> user_data<span class="gtkdoc opt">);</span>
+<span class="keyword">static</span><span class="normal"> </span><span class="type">void</span>
+<span class="function">log_handler</span><span class="normal"> </span><span class="symbol">(</span><span class="keyword">const</span><span class="normal"> </span><span class="usertype">gchar</span><span class="normal">   </span><span class="symbol">*</span><span class="normal">log_domain</span><span class="symbol">,</span>
+<span class="normal">             </span><span class="usertype">GLogLevelFlags</span><span class="normal"> log_level</span><span class="symbol">,</span>
+<span class="normal">             </span><span class="keyword">const</span><span class="normal"> </span><span class="usertype">gchar</span><span class="normal">   </span><span class="symbol">*</span><span class="normal">message</span><span class="symbol">,</span>
+<span class="normal">             </span><span class="usertype">gpointer</span><span class="normal">       user_data</span><span class="symbol">)</span>
+<span class="cbracket">{</span>
+<span class="normal">  </span><span class="function"><a href="glib-Message-Logging.html#g-log-default-handler">g_log_default_handler</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">log_domain</span><span class="symbol">,</span><span class="normal"> log_level</span><span class="symbol">,</span><span class="normal"> message</span><span class="symbol">,</span><span class="normal"> user_data</span><span class="symbol">);</span>
-  <span class="function"><a href="glib-Warnings-and-Assertions.html#g-on-error-query">g_on_error_query</a></span> <span class="gtkdoc opt">(</span>MY_PROGRAM_NAME<span class="gtkdoc opt">);</span>
-<span class="gtkdoc opt">}</span>
+<span class="normal">  </span><span class="function"><a href="glib-Warnings-and-Assertions.html#g-on-error-query">g_on_error_query</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">MY_PROGRAM_NAME</span><span class="symbol">);</span>
+<span class="cbracket">}</span>
-<span class="gtkdoc kwb">int</span>
-<span class="function">main</span> <span class="gtkdoc opt">(</span><span class="gtkdoc kwb">int</span> argc<span class="gtkdoc opt">,</span> <span class="gtkdoc kwb">char</span> <span class="gtkdoc opt">*</span>argv<span class="gtkdoc opt">[])</span>
-<span class="gtkdoc opt">{</span>
-  <span class="function"><a href="glib-Message-Logging.html#g-log-set-handler">g_log_set_handler</a></span> <span class="gtkdoc opt">(</span>MY_LOG_DOMAIN<span class="gtkdoc opt">,</span>
-                     G_LOG_LEVEL_WARNING <span class="gtkdoc opt">|</span>
-                     G_LOG_LEVEL_ERROR <span class="gtkdoc opt">|</span>
-                     G_LOG_LEVEL_CRITICAL<span class="gtkdoc opt">,</span>
-                     log_handler<span class="gtkdoc opt">,</span>
-                     NULL<span class="gtkdoc opt">);</span>
-  <span class="gtkdoc opt">...</span></pre></td>
+<span class="type">int</span>
+<span class="function">main</span><span class="normal"> </span><span class="symbol">(</span><span class="type">int</span><span class="normal"> argc</span><span class="symbol">,</span><span class="normal"> </span><span class="type">char</span><span class="normal"> </span><span class="symbol">*</span><span class="normal">argv</span><span class="symbol">[])</span>
+<span class="cbracket">{</span>
+<span class="normal">  </span><span class="function"><a href="glib-Message-Logging.html#g-log-set-handler">g_log_set_handler</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">MY_LOG_DOMAIN</span><span class="symbol">,</span>
+<span class="normal">                     <a href="glib-Message-Logging.html#G-LOG-LEVEL-WARNING:CAPS">G_LOG_LEVEL_WARNING</a> </span><span class="symbol">|</span>
+<span class="normal">                     <a href="glib-Message-Logging.html#G-LOG-LEVEL-ERROR:CAPS">G_LOG_LEVEL_ERROR</a> </span><span class="symbol">|</span>
+<span class="normal">                     <a href="glib-Message-Logging.html#G-LOG-LEVEL-CRITICAL:CAPS">G_LOG_LEVEL_CRITICAL</a></span><span class="symbol">,</span>
+<span class="normal">                     log_handler</span><span class="symbol">,</span>
+<span class="normal">                     <a href="glib-Standard-Macros.html#NULL:CAPS">NULL</a></span><span class="symbol">);</span>
+<span class="normal">  </span><span class="symbol">...</span></pre></td>
       </tr>
     </tbody>
   </table>
@@ -530,7 +550,7 @@ a stack trace. The prompt is then shown again.</p>
 option. If <em class="parameter"><code>prg_name</code></em>
 is <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>, <a class="link" href="glib-Miscellaneous-Utility-Functions.html#g-get-prgname" title="g_get_prgname ()"><code class="function">g_get_prgname()</code></a> is called to get
 the program name (which will work correctly if <code class="function">gdk_init()</code> or
-<a href="../gtk4/gtk4-General.html#gtk-init"><code class="function">gtk_init()</code></a> has been called)</p></td>
+<code class="function">gtk_init()</code> has been called)</p></td>
 <td class="parameter_annotations"> </td>
 </tr></tbody>
 </table></div>
@@ -544,7 +564,7 @@ g_on_error_stack_trace (<em class="parameter"><code>const <a class="link" href="
 <p>Invokes gdb, which attaches to the current process and shows a
 stack trace. Called by <a class="link" href="glib-Warnings-and-Assertions.html#g-on-error-query" title="g_on_error_query ()"><code class="function">g_on_error_query()</code></a> when the "[S]tack trace"
 option is selected. You can get the current process's program name
-with <a class="link" href="glib-Miscellaneous-Utility-Functions.html#g-get-prgname" title="g_get_prgname ()"><code class="function">g_get_prgname()</code></a>, assuming that you have called <a href="../gtk4/gtk4-General.html#gtk-init"><code class="function">gtk_init()</code></a> or
+with <a class="link" href="glib-Miscellaneous-Utility-Functions.html#g-get-prgname" title="g_get_prgname ()"><code class="function">g_get_prgname()</code></a>, assuming that you have called <code class="function">gtk_init()</code> or
 <code class="function">gdk_init()</code>.</p>
 <p>This function may cause different actions on non-UNIX platforms.</p>
 <div class="refsect3">
@@ -579,6 +599,6 @@ and on other architectures it raises a <code class="literal">SIGTRAP</code> sign
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-Windows-Compatibility-Functions.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib-utilities.html" title="GLib Utilities">
 <link rel="prev" href="glib-UNIX-specific-utilities-and-integration.html" title="UNIX-specific utilities and integration">
 <link rel="next" href="glib-GUuid.html" title="GUuid">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -149,7 +149,7 @@
 </div>
 <div class="refsect1">
 <a name="glib-Windows-Compatibility-Functions.includes"></a><h2>Includes</h2>
-<pre class="synopsis">#include &lt;glib.h&gt;
+<pre class="synopsis">#include &lt;gmodule.h&gt;
 </pre>
 </div>
 <div class="refsect1">
@@ -239,7 +239,7 @@ This will get the "full Unicode" commandline arguments using
 <code class="function">GetCommandLineW()</code> and convert it to the GLib filename encoding (which
 is UTF-8 on Windows).</p>
 <p>The strings returned by this function are suitable for use with
-functions such as <a class="link" href="glib-File-Utilities.html#g-open" title="g_open ()"><code class="function">g_open()</code></a> and <a href="../gio/GFile.html#g-file-new-for-commandline-arg"><code class="function">g_file_new_for_commandline_arg()</code></a> but
+functions such as <a class="link" href="glib-File-Utilities.html#g-open" title="g_open ()"><code class="function">g_open()</code></a> and <a href="../GFile.html#g-file-new-for-commandline-arg"><code class="function">g_file_new_for_commandline_arg()</code></a> but
 are not suitable for use with <a class="link" href="glib-Commandline-option-parser.html#g-option-context-parse" title="g_option_context_parse ()"><code class="function">g_option_context_parse()</code></a>, which assumes
 that its input will be in the system codepage.  The return value is
 suitable for use with <a class="link" href="glib-Commandline-option-parser.html#g-option-context-parse-strv" title="g_option_context_parse_strv ()"><code class="function">g_option_context_parse_strv()</code></a>, however, which
@@ -248,7 +248,7 @@ is a better match anyway because it won't leak memory.</p>
 be freed with <a class="link" href="glib-String-Utility-Functions.html#g-strfreev" title="g_strfreev ()"><code class="function">g_strfreev()</code></a> when no longer needed.</p>
 <div class="refsect3">
 <a name="g-win32-get-command-line.returns"></a><h4>Returns</h4>
-<p> the commandline arguments in the GLib
+<p>the commandline arguments in the GLib
 filename encoding (ie: UTF-8). </p>
 <p><span class="annotation">[<acronym title="Free data after the code is done."><span class="acronym">transfer full</span></acronym>]</span></p>
 </div>
@@ -369,12 +369,12 @@ the same way as above.</p>
 <tbody>
 <tr>
 <td class="parameter_name"><p>package</p></td>
-<td class="parameter_description"><p> You should pass <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a> for this. </p></td>
+<td class="parameter_description"><p>You should pass <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a> for this. </p></td>
 <td class="parameter_annotations"><span class="annotation">[<acronym title="NULL may be passed as the value in, out, in-out; or as a return value."><span class="acronym">nullable</span></acronym>]</span></td>
 </tr>
 <tr>
 <td class="parameter_name"><p>dll_name</p></td>
-<td class="parameter_description"><p> The name of a DLL that a package provides in UTF-8, or <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>. </p></td>
+<td class="parameter_description"><p>The name of a DLL that a package provides in UTF-8, or <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>. </p></td>
 <td class="parameter_annotations"><span class="annotation">[<acronym title="NULL may be passed as the value in, out, in-out; or as a return value."><span class="acronym">nullable</span></acronym>]</span></td>
 </tr>
 </tbody>
@@ -427,7 +427,7 @@ function passing the DLL handle.</p>
 </colgroup>
 <tbody><tr>
 <td class="parameter_name"><p>hmodule</p></td>
-<td class="parameter_description"><p> The Win32 handle for a DLL loaded into the current process, or <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>. </p></td>
+<td class="parameter_description"><p>The Win32 handle for a DLL loaded into the current process, or <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>. </p></td>
 <td class="parameter_annotations"><span class="annotation">[<acronym title="NULL may be passed as the value in, out, in-out; or as a return value."><span class="acronym">nullable</span></acronym>]</span></td>
 </tr></tbody>
 </table></div>
@@ -482,12 +482,12 @@ as <em class="parameter"><code>package</code></em>
 <tbody>
 <tr>
 <td class="parameter_name"><p>package</p></td>
-<td class="parameter_description"><p> You should pass <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a> for this. </p></td>
+<td class="parameter_description"><p>You should pass <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a> for this. </p></td>
 <td class="parameter_annotations"><span class="annotation">[<acronym title="NULL may be passed as the value in, out, in-out; or as a return value."><span class="acronym">nullable</span></acronym>]</span></td>
 </tr>
 <tr>
 <td class="parameter_name"><p>dll_name</p></td>
-<td class="parameter_description"><p> The name of a DLL that a package provides, in UTF-8, or <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>. </p></td>
+<td class="parameter_description"><p>The name of a DLL that a package provides, in UTF-8, or <a class="link" href="glib-Standard-Macros.html#NULL:CAPS" title="NULL"><code class="literal">NULL</code></a>. </p></td>
 <td class="parameter_annotations"><span class="annotation">[<acronym title="NULL may be passed as the value in, out, in-out; or as a return value."><span class="acronym">nullable</span></acronym>]</span></td>
 </tr>
 <tr>
@@ -694,6 +694,6 @@ macro <a class="link" href="glib-Windows-Compatibility-Functions.html#MAXPATHLEN
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/glib/glib-building.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="glib.html" title="GLib Overview">
 <link rel="prev" href="glib.html" title="GLib Overview">
 <link rel="next" href="glib-cross-compiling.html" title="Cross-compiling the GLib package">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -56,9 +56,16 @@
       <span class="command"><strong>./configure --help</strong></span> for information about
       the standard options.
     </p>
+<p>
+      GLib is compiled with
+      <a class="ulink" href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fstrict-aliasing" target="_top">strict aliasing</a>
+      disabled. It is strongly recommended that this is not re-enabled by
+      overriding the compiler flags, as GLib has not been tested with strict
+      aliasing and cannot be guaranteed to work.
+    </p>
 <p>
       The GTK+ documentation contains
-      <a class="ulink" href="../gtk/gtk-building.html" target="_top">further details</a>
+      <a class="ulink" href="https://developer.gnome.org/gtk3/stable/gtk-building.html" target="_top">further details</a>
       about the build process and ways to influence it.
     </p>
 </div>
@@ -67,25 +74,22 @@
 <p>
       Before you can compile the GLib library, you need to have
       various other tools and libraries installed on your system.
-      Beyond a C compiler (which must implement C90, but does not need
-      to implement C99), the two tools needed during the build process
-      (as differentiated from the tools used in when creating GLib
-      mentioned above such as <span class="application">autoconf</span>) are
-      <span class="command"><strong>pkg-config</strong></span> and GNU make.
+      If you are building from a release archive, you will need
+      <a class="ulink" href="https://wiki.gnome.org/Projects/GLib/CompilerRequirements" target="_top">a compliant C toolchain</a>,
+      GNU Make, and <span class="application">pkg-config</span>;
+      if you are building directly from a Git repository clone
+      of GLib, you will also need the GNU Autotools mentioned
+      above.
     </p>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
 <li class="listitem"><p>
-          <a class="ulink" href="http://www.freedesktop.org/software/pkgconfig/" target="_top">pkg-config</a>
+          <a class="ulink" href="https://www.freedesktop.org/wiki/Software/pkg-config/" target="_top">pkg-config</a>
           is a tool for tracking the compilation flags needed for
           libraries that are used by the GLib library. (For each
           library, a small <code class="literal">.pc</code> text file is
           installed in a standard location that contains the compilation
           flags needed for that library along with version number
-          information.) The version of <span class="command"><strong>pkg-config</strong></span>
-          needed to build GLib is mirrored in the
-          <code class="filename">dependencies</code> directory
-          on the <a class="ulink" href="ftp://ftp.gtk.org/pub/gtk/v2.2/" target="_top">GTK+ FTP
-          site.</a>
+          information).
         </p></li>
 <li class="listitem"><p>
           The GLib Makefiles make use of several features specific to
@@ -118,7 +122,7 @@
 <p>
           If your system has an <code class="function">iconv()</code> implementation but
           you want to use libiconv instead, you can pass the
-          --with-libiconv option to configure. This forces
+          <code class="option">--with-libiconv</code> option to configure. This forces
           libiconv to be used.
         </p>
 <p>
@@ -156,18 +160,19 @@
         </p></li>
 <li class="listitem"><p>
           GRegex uses the <a class="ulink" href="http://www.pcre.org/" target="_top">PCRE library</a>
-          for regular expression matching. The default is to use the internal
-          version of PCRE that is patched to use GLib for memory management
-          and Unicode handling. If you prefer to use the system-supplied PCRE
-          library  you can pass the <code class="option">--with-pcre=system</code> option
-          to, but it is not recommended.
+          for regular expression matching. The default is to use the system
+          version of PCRE, to reduce the chances of security fixes going out
+          of sync. GLib additionally provides an internal copy of PCRE in case
+          the system version is too old, or does not support UTF-8; the internal
+          copy is patched to use GLib for memory management and to share the
+          same Unicode tables.
         </p></li>
 <li class="listitem"><p>
           The optional extended attribute support in GIO requires the
-          getxattr() family of functions that may be provided by glibc or
-          by the standalone libattr library. To build GLib without extended
-          attribute support, use the <code class="option">--disable-xattr</code>
-          option.
+          <code class="function">getxattr()</code> family of functions that may be
+          provided by the C library or by the standalone libattr library. To
+          build GLib without extended attribute support, use the
+          <code class="option">--disable-xattr</code> option.
         </p></li>
 <li class="listitem"><p>
           The optional SELinux support in GIO requires libselinux.
@@ -184,7 +189,9 @@
           The optional support for
           <a class="ulink" href="http://sourceware.org/systemtap/" target="_top">SystemTap</a>
           can be disabled with the <code class="option">--disable-systemtap</code>
-          configure option.
+          configure option. Additionally, you can control the location
+          where GLib installs the SystemTap probes, using the
+          <code class="option">--with-tapset-install-dir=DIR</code> configure option.
         </p></li>
 </ul></div>
 </div>
@@ -195,40 +202,41 @@
       <span class="command"><strong>configure</strong></span> script in the GLib
       library supports these additional arguments:
     </p>
-<p><b><code class="systemitem">--enable-debug</code>. </b>
+<p><b><code class="option">--enable-debug</code>. </b>
         Turns on various amounts of debugging support. Setting this to 'no'
-        disables g_assert(), g_return_if_fail(), g_return_val_if_fail() and
-        all cast checks between different object types. Setting it to 'minimum'         disables only cast checks. Setting it to 'yes' enables
-        <a class="link" href="glib-running.html#G-DEBUG:CAPS" title="G_DEBUG">runtime debugging</a>.
-        The default is 'minimum'.
-        Note that 'no' is fast, but dangerous as it tends to destabilize
+        disables <code class="function">g_assert()</code>, <code class="function">g_return_if_fail()</code>,
+        <code class="function">g_return_val_if_fail()</code> and all cast checks
+        between different object types. Setting it to 'minimum' disables
+        only cast checks. Setting it to 'yes' enables <a class="link" href="glib-running.html#G-DEBUG:CAPS" title="G_DEBUG">runtime debugging</a>.
+        The default is 'minimum' for stable releases, and 'yes' for development
+        snapshots. Note that 'no' is fast, but dangerous as it tends to destabilize
         even mostly bug-free software by changing the effect of many bugs
         from simple warnings into fatal crashes. Thus
         <code class="option">--enable-debug=no</code> should <span class="emphasis"><em>not</em></span>
         be used for stable releases of GLib.
       </p>
-<p><b><code class="systemitem">--disable-gc-friendly</code> and
-        <code class="systemitem">--enable-gc-friendly</code>. </b>
-        By default, and with <code class="systemitem">--disable-gc-friendly</code>
-        as well, Glib does not clear the memory for certain objects before
-        they are freed. For example, Glib may decide to recycle GList nodes
+<p><b><code class="option">--disable-gc-friendly</code> and
+        <code class="option">--enable-gc-friendly</code>. </b>
+        By default, and with <code class="option">--disable-gc-friendly</code>
+        as well, GLib does not clear the memory for certain objects before
+        they are freed. For example, GLib may decide to recycle GList nodes
         by putting them in a free list. However, memory profiling and debugging
         tools like <a class="ulink" href="http://www.valgrind.org" target="_top">Valgrind</a> work
         better if an application does not keep dangling pointers to freed
         memory (even though these pointers are no longer dereferenced), or
         invalid pointers inside uninitialized memory.
-        The <code class="systemitem">--enable-gc-friendly</code> option makes Glib
+        The <code class="option">--enable-gc-friendly</code> option makes GLib
         clear memory in these situations:
       </p>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
 <li class="listitem"><p>
-            When shrinking a GArray, Glib will clear the memory no longer
+            When shrinking a GArray, GLib will clear the memory no longer
             available in the array: shrink an array from 10 bytes to 7, and
             the last 3 bytes will be cleared. This includes removals of single
             and multiple elements.
           </p></li>
 <li class="listitem"><p>
-            When growing a GArray, Glib will clear the new chunk of memory.
+            When growing a GArray, GLib will clear the new chunk of memory.
             Grow an array from 7 bytes to 10 bytes, and the last 3 bytes will
             be cleared.
           </p></li>
@@ -236,22 +244,22 @@
             The above applies to GPtrArray as well.
           </p></li>
 <li class="listitem"><p>
-            When freeing a node from a GHashTable, Glib will first clear
+            When freeing a node from a GHashTable, GLib will first clear
             the node, which used to have pointers to the key and the value
             stored at that node.
           </p></li>
 <li class="listitem"><p>
-            When destroying or removing a GTree node, Glib will clear the node,
+            When destroying or removing a GTree node, GLib will clear the node,
             which used to have pointers to the node's value, and the left and
             right subnodes.
           </p></li>
 </ul></div>
 <p>
         Since clearing the memory has a cost,
-        <code class="systemitem">--disable-gc-friendly</code> is the default.
+        <code class="option">--disable-gc-friendly</code> is the default.
       </p>
-<p><b><code class="systemitem">--disable-mem-pools</code> and
-        <code class="systemitem">--enable-mem-pools</code>. </b>
+<p><b><code class="option">--disable-mem-pools</code> and
+        <code class="option">--enable-mem-pools</code>. </b>
         Many small chunks of memory are often allocated via collective pools
         in GLib and are cached after release to speed up reallocations.
         For sparse memory systems this behaviour is often inferior, so
@@ -280,19 +288,12 @@
 </ul></div>
 <p>
       </p>
-<p><b><code class="systemitem">--with-threads</code>. </b>
+<p><b><code class="option">--with-threads</code>. </b>
         Specify a thread implementation to use. Available options are
         'posix' or 'win32'. Normally, <span class="command"><strong>configure</strong></span>
         should be able to work out the system threads API on its own.
       </p>
-<p><b><code class="systemitem">--disable-regex</code> and
-        <code class="systemitem">--enable-regex</code>. </b>
-        Do not compile GLib with regular expression support.
-        GLib will be smaller because it will not need the
-        PCRE library. This is however not recommended, as
-        programs may need GRegex.
-      </p>
-<p><b><code class="systemitem">--with-pcre</code>. </b>
+<p><b><code class="option">--with-pcre</code>. </b>
         Specify whether to use the internal or the system-supplied
         PCRE library.
         </p>
@@ -303,47 +304,54 @@
             </p></li>
 <li class="listitem"><p>
               'system' means that GRegex will be compiled to use
-              the system-supplied PCRE library.
+              the system-supplied PCRE library; this is the default
+              setting.
             </p></li>
 </ul></div>
 <p>
-        Using the internal PCRE is the preferred solution:
+        Using the internal PCRE is the preferred solution if:
         </p>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
 <li class="listitem"><p>
-              System-supplied PCRE has a separated copy of the big tables
-              used for Unicode handling.
+              your system has strict resource constraints; the system-supplied
+              PCRE has a separated copy of the tables used for Unicode
+              handling, whereas the internal copy shares the Unicode tables
+              used by GLib.
             </p></li>
 <li class="listitem"><p>
-              Some systems have PCRE libraries compiled without some needed
-              features, such as UTF-8 and Unicode support.
+              your system has PCRE built without some needed features,
+              such as UTF-8 and Unicode support.
             </p></li>
 <li class="listitem"><p>
-              PCRE uses some global variables for memory management and
-              other features. In the rare case of a program using both
-              GRegex and PCRE (maybe indirectly through a library),
-              this variables could lead to problems when they are modified.
+              you are planning to use both GRegex and PCRE API at the same
+              time, either directly or indirectly through a dependency; PCRE
+              uses some global variables for memory management and
+              other features, and if both GLib and PCRE try to access them
+              at the same time, this could lead to undefined behavior.
             </p></li>
 </ul></div>
 <p>
       </p>
-<p><b><code class="systemitem">--disable-included-printf</code> and
-        <code class="systemitem">--enable-included-printf</code>. </b>
+<p><b><code class="option">--disable-included-printf</code> and
+        <code class="option">--enable-included-printf</code>. </b>
         By default the <span class="command"><strong>configure</strong></span> script will try
         to auto-detect whether the C library provides a suitable set
-        of printf() functions. In detail, <span class="command"><strong>configure</strong></span>
-        checks that the semantics of snprintf() are as specified by C99
+        of <code class="function">printf()</code> functions. In detail,
+        <span class="command"><strong>configure</strong></span> checks that the semantics of
+        <code class="function">snprintf()</code> are as specified by C99
         and that positional parameters as specified in the Single Unix
         Specification are supported. If this not the case, GLib will
-        include an implementation of the printf() family.
+        include an implementation of the <code class="function">printf()</code>
+        family.
         These options can be used to explicitly control whether
-        an implementation of the printf() family should be included or not.
+        an implementation of the <code class="function">printf()</code> family
+        should be included or not.
       </p>
-<p><b><code class="systemitem">--disable-Bsymbolic</code> and
-        <code class="systemitem">--enable-Bsymbolic</code>. </b>
-        By default, GLib uses the -Bsymbolic-functions linker
-        flag to avoid intra-library PLT jumps. A side-effect
+<p><b><code class="option">--disable-Bsymbolic</code> and
+        <code class="option">--enable-Bsymbolic</code>. </b>
+        By default, GLib uses the <code class="option">-Bsymbolic-functions</code>
+        linker flag to avoid intra-library PLT jumps. A side-effect
         of this is that it is no longer possible to override
         internal uses of GLib functions with
         <code class="envar">LD_PRELOAD</code>. Therefore, it may make
@@ -351,8 +359,8 @@
         The <code class="option">--disable-Bsymbolic</code> option allows
         to do that.
       </p>
-<p><b><code class="systemitem">--disable-gtk-doc</code> and
-        <code class="systemitem">--enable-gtk-doc</code>. </b>
+<p><b><code class="option">--disable-gtk-doc</code> and
+        <code class="option">--enable-gtk-doc</code>. </b>
         By default the <span class="command"><strong>configure</strong></span> script will try
         to auto-detect whether the
         <span class="application">gtk-doc</span> package is installed.
@@ -364,8 +372,8 @@
         pre-generated HTML files will be installed instead of
         building them on your machine.
       </p>
-<p><b><code class="systemitem">--disable-man</code> and
-        <code class="systemitem">--enable-man</code>. </b>
+<p><b><code class="option">--disable-man</code> and
+        <code class="option">--enable-man</code>. </b>
         By default the <span class="command"><strong>configure</strong></span> script will try
         to auto-detect whether <span class="application">xsltproc</span>
         and the necessary Docbook stylesheets are installed.
@@ -375,63 +383,64 @@
         used or not. The distribution includes pre-generated man
         pages.
       </p>
-<p><b><code class="systemitem">--disable-xattr</code> and
-        <code class="systemitem">--enable-xattr</code>. </b>
+<p><b><code class="option">--disable-xattr</code> and
+        <code class="option">--enable-xattr</code>. </b>
         By default the <span class="command"><strong>configure</strong></span> script will try
-        to auto-detect whether the getxattr() family of functions
-        is available. If it is, then extended attribute support
-        will be included in GIO. These options can be used to
-        explicitly control whether extended attribute support
-        should be included or not. getxattr() and friends can
-        be provided by glibc or by the standalone libattr library.
+        to auto-detect whether the <code class="function">getxattr()</code>
+        family of functions is available. If it is, then extended
+        attribute support will be included in GIO. These options can
+        be used to explicitly control whether extended attribute
+        support should be included or not. <code class="function">getxattr()</code>
+        and friends can be provided by glibc or by the standalone
+        libattr library.
       </p>
-<p><b><code class="systemitem">--disable-selinux</code> and
-        <code class="systemitem">--enable-selinux</code>. </b>
+<p><b><code class="option">--disable-selinux</code> and
+        <code class="option">--enable-selinux</code>. </b>
         By default the <span class="command"><strong>configure</strong></span> script will
         auto-detect if libselinux is available and include
         SELinux support in GIO if it is. These options can be
         used to explicitly control whether SELinux support should
         be included.
       </p>
-<p><b><code class="systemitem">--disable-dtrace</code> and
-        <code class="systemitem">--enable-dtrace</code>. </b>
+<p><b><code class="option">--disable-dtrace</code> and
+        <code class="option">--enable-dtrace</code>. </b>
         By default the <span class="command"><strong>configure</strong></span> script will
         detect if DTrace support is available, and use it.
       </p>
-<p><b><code class="systemitem">--disable-systemtap</code> and
-        <code class="systemitem">--enable-systemtap</code>. </b>
+<p><b><code class="option">--disable-systemtap</code> and
+        <code class="option">--enable-systemtap</code>. </b>
         This option requires DTrace support. If it is available, then
         the <span class="command"><strong>configure</strong></span> script will also check for
         the presence of SystemTap.
       </p>
-<p><b><code class="systemitem">--enable-coverage</code> and
-        <code class="systemitem">--disable-coverage</code>. </b>
+<p><b><code class="option">--enable-coverage</code> and
+        <code class="option">--disable-coverage</code>. </b>
         Enable the generation of coverage reports for the GLib tests.
         This requires the lcov frontend to gcov from the
         <a class="ulink" href="http://ltp.sourceforge.net" target="_top">Linux Test Project</a>.
         To generate a coverage report, use the lcov make target. The
         report is placed in the <code class="filename">glib-lcov</code> directory.
       </p>
-<p><b><code class="systemitem">--with-runtime-libdir=RELPATH</code>. </b>
+<p><b><code class="option">--with-runtime-libdir=RELPATH</code>. </b>
         Allows specifying a relative path to where to install the runtime
         libraries (meaning library files used for running, not developing,
         GLib applications). This can be used in operating system setups where
         programs using GLib needs to run before e.g. <code class="filename">/usr</code>
         is mounted.
-        For example, if LIBDIR is <code class="filename">/usr/lib</code> and
+        For example, if <code class="varname">LIBDIR</code> is <code class="filename">/usr/lib</code> and
         <code class="filename">../../lib</code> is passed to
-        <code class="systemitem">--with-runtime-libdir</code> then the
+        <code class="option">--with-runtime-libdir</code> then the
         runtime libraries are installed into <code class="filename">/lib</code> rather
         than <code class="filename">/usr/lib</code>.
       </p>
-<p><b><code class="systemitem">--with-python</code>. </b>
+<p><b><code class="option">--with-python=PATH</code>. </b>
         Allows specifying the Python interpreter to use, either as an absolute path,
-        or as a program name. GLib can be built with Python 2 (at least version 2.5)
-        or Python 3.
+        or as a program name. GLib can be built with Python 2 (at least version 2.7)
+        or, preferably, with Python 3.
       </p>
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>