RubyGems - gio2 - Versions diffs - 0.90.3-x86-mingw32 - Mend

gio2 0.90.3-x86-mingw32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (856) hide show

data/vendor/local/share/gtk-doc/html/glib/glib-changes.html ADDED

@@ -0,0 +1,159 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Changes to GLib</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GLib Reference Manual">
+<link rel="up" href="glib.html" title="GLib Overview">
+<link rel="prev" href="glib-running.html" title="Running GLib Applications">
+<link rel="next" href="glib-regex-syntax.html" title="Regular expression syntax">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="glib-running.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="glib.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GLib Reference Manual</th>
+<td><a accesskey="n" href="glib-regex-syntax.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="refentry">
+<a name="glib-changes"></a><div class="titlepage"></div>
+<div class="refnamediv"><table width="100%"><tr>
+<td valign="top">
+<h2><span class="refentrytitle">Changes to GLib</span></h2>
+<p>Changes to GLib —
+Incompatible changes made between successing versions of GLib
+</p>
+</td>
+<td valign="top" align="right"></td>
+</tr></table></div>
+<div class="refsect1">
+<a name="id561689"></a><h2>Incompatible changes from 2.0 to 2.2</h2>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+<p>
+GLib changed the seeding algorithm for the pseudo-random number
+generator Mersenne Twister, as used by <span class="structname">GRand</span>
+and <span class="structname">GRandom</span>. This was necessary, because some
+seeds would yield very bad pseudo-random streams. Also the
+pseudo-random integers generated by
+<code class="function">g_rand*_int_range()</code> will have a
+slightly better equal distribution with the new version of GLib.
+</p>
+<p>
+Further information can be found at the website of the Mersenne
+Twister random number generator at <a class="ulink" href="http://www.math.keio.ac.jp/~matumoto/emt.html" target="_top">http://www.math.keio.ac.jp/~matumoto/emt.html</a>.
+</p>
+<p>
+The original seeding and generation algorithms, as found in GLib
+2.0.x, can be used instead of the new ones by setting the environment
+variable <code class="envar">G_RANDOM_VERSION</code> to the value of '2.0'. Use
+the GLib-2.0 algorithms only if you have sequences of numbers generated
+with Glib-2.0 that you need to reproduce exactly.
+</p>
+</li></ul></div>
+</div>
+<div class="refsect1">
+<a name="id537002"></a><h2>Incompatible changes from 1.2 to 2.0</h2>
+<p>
+The <a class="ulink" href="http://developer.gnome.org/dotplan/porting/" target="_top">GNOME 2.0
+porting guide</a> on <a class="ulink" href="http://developer.gnome.org" target="_top">http://developer.gnome.org</a>
+has some more detailed discussion of porting from 1.2 to 2.0.
+See the section on GLib.
+</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+<p>
+The event loop functionality <span class="structname">GMain</span> has extensively
+been revised to support multiple separate main loops in separate threads.
+All sources (timeouts, idle functions, etc.) are associated with a
+<span class="structname">GMainContext</span>.
+</p>
+<p>
+Compatibility functions exist so that most application code dealing with
+the main loop will continue to work. However, code that creates new custom
+types of sources will require modification.
+</p>
+<p>
+The main changes here are:
+  </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="circle">
+<li class="listitem"><p>
+   Sources are now exposed as <span class="type">GSource *</span>, rather than simply as
+   numeric ids.
+  </p></li>
+<li class="listitem"><p>
+   New types of sources are created by structure "derivation" from
+   <span class="structname">GSource</span>, so the <code class="literal">source_data</code>
+   parameter to the <span class="structname">GSource</span> virtual functions has been
+   replaced with a <span class="type">GSource *</span>.
+  </p></li>
+<li class="listitem"><p>
+   Sources are first created, then later added to a specific
+   <span class="structname">GMainContext</span>.
+  </p></li>
+<li class="listitem"><p>
+   Dispatching has been modified so both the callback and data are passed
+   in to the <code class="function">dispatch()</code> virtual function.
+  </p></li>
+</ul></div>
+<p>
+  To go along with this change, the vtable for
+  <span class="structname">GIOChannel</span> has changed and
+  <code class="function">add_watch()</code> has been replaced by
+  <code class="function">create_watch()</code>.
+</p>
+</li>
+<li class="listitem">
+<p>
+<code class="function">g_list_foreach()</code> and
+<code class="function">g_slist_foreach()</code> have been changed so they
+are now safe against removal of the current item, not the next item.
+</p>
+<p>
+It's not recommended to mutate the list in the callback to these
+functions in any case.
+</p>
+</li>
+<li class="listitem"><p>
+<span class="structname">GDate</span> now works in UTF-8, not in the current locale.
+If you want to use it with the encoding of the locale, you need to convert
+strings using <code class="function">g_locale_to_utf8()</code> first.
+</p></li>
+<li class="listitem">
+<p>
+<code class="function">g_strsplit()</code> has been fixed to:
+  </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="circle">
+<li class="listitem"><p>
+   include trailing empty tokens, rather than stripping them
+  </p></li>
+<li class="listitem"><p>
+   split into a maximum of <code class="literal">max_tokens</code> tokens, rather
+   than <code class="literal">max_tokens + 1</code>
+  </p></li>
+</ul></div>
+<p>
+  Code depending on either of these bugs will need to be fixed.
+</p>
+</li>
+<li class="listitem"><p>
+Deprecated functions that got removed:
+<code class="function">g_set_error_handler()</code>,
+<code class="function">g_set_warning_handler()</code>,
+<code class="function">g_set_message_handler()</code>, use
+<code class="function">g_log_set_handler()</code> instead.
+</p></li>
+</ul></div>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/glib/glib-compiling.html ADDED

@@ -0,0 +1,118 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Compiling GLib Applications</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GLib Reference Manual">
+<link rel="up" href="glib.html" title="GLib Overview">
+<link rel="prev" href="glib-cross-compiling.html" title="Cross-compiling the GLib package">
+<link rel="next" href="glib-running.html" title="Running GLib Applications">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="glib-cross-compiling.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="glib.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GLib Reference Manual</th>
+<td><a accesskey="n" href="glib-running.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="refentry">
+<a name="glib-compiling"></a><div class="titlepage"></div>
+<div class="refnamediv"><table width="100%"><tr>
+<td valign="top">
+<h2><span class="refentrytitle">Compiling GLib Applications</span></h2>
+<p>Compiling GLib Applications —
+How to compile your GLib application
+</p>
+</td>
+<td valign="top" align="right"></td>
+</tr></table></div>
+<div class="refsect1">
+<a name="id557847"></a><h2>Compiling GLib Applications on UNIX</h2>
+<p>
+To compile a GLib application, you need to tell the compiler where to
+find the GLib header files and libraries. This is done with the
+<span class="application">pkg-config</span> utility.
+</p>
+<p>
+The following interactive shell session demonstrates how
+<span class="application">pkg-config</span> is used (the actual output on
+your system may be different):
+</p>
+<pre class="programlisting">
+$ pkg-config --cflags glib-2.0
+ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
+$ pkg-config --libs glib-2.0
+ -L/usr/lib -lm -lglib-2.0
+</pre>
+<p>
+</p>
+<p>
+If your application uses threads or <span class="structname">GObject</span>
+features, it must be compiled and linked with the options returned by the
+following <span class="application">pkg-config</span> invocations:
+</p>
+<pre class="programlisting">
+$ pkg-config --cflags --libs gthread-2.0
+$ pkg-config --cflags --libs gobject-2.0
+</pre>
+<p>
+</p>
+<p>
+If your application uses modules, it must be compiled and linked with the options
+returned by one of the following <span class="application">pkg-config</span> invocations:
+</p>
+<pre class="programlisting">
+$ pkg-config --cflags --libs gmodule-no-export-2.0
+$ pkg-config --cflags --libs gmodule-2.0
+</pre>
+<p>
+The difference between the two is that gmodule-2.0 adds <code class="option">--export-dynamic</code>
+to the linker flags, which is often not needed.
+</p>
+<p>
+The simplest way to compile a program is to use the "backticks"
+feature of the shell. If you enclose a command in backticks
+(<span class="emphasis"><em>not single quotes</em></span>), then its output will be
+substituted into the command line before execution. So to compile
+a GLib Hello, World, you would type the following:
+</p>
+<pre class="programlisting">
+$ cc `pkg-config --cflags --libs glib-2.0` hello.c -o hello
+</pre>
+<p>
+</p>
+<p>
+If you want to make sure that your program doesn't use any deprecated
+functions, you can define the preprocessor symbol G_DISABLE_DEPRECATED
+by using the command line option <code class="literal">-DG_DISABLE_DEPRECATED=1</code>.
+</p>
+<p>
+The recommended way of using GLib has always been to only include the
+toplevel headers <code class="filename">glib.h</code>,
+<code class="filename">glib-object.h</code>, <code class="filename">gio.h</code>.
+Still, there are some exceptions; these headers have to be included separately:
+<code class="filename">gmodule.h</code>,
+<code class="filename">glib/gi18n-lib.h</code> or <code class="filename">glib/gi18n.h</code> (see
+the <a class="link" href="glib-I18N.html" title="Internationalization">Internationalization section</a>),
+<code class="filename">glib/gprintf.h</code> and <code class="filename">glib/gstdio.h</code>
+(we don't want to pull in all of stdio).
+</p>
+<p>
+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
+headers (it <span class="emphasis"><em>is</em></span> turned on for GObject and GIO).
+To turn it on, define the preprocessor symbol G_DISABLE_SINGLE_INCLUDES
+by using the command line option <code class="literal">-DG_DISABLE_SINGLE_INCLUDES</code>.
+</p>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/glib/glib-core.html ADDED

@@ -0,0 +1,64 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>GLib Core Application Support</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GLib Reference Manual">
+<link rel="up" href="index.html" title="GLib Reference Manual">
+<link rel="prev" href="glib-Atomic-Operations.html" title="Atomic Operations">
+<link rel="next" href="glib-The-Main-Event-Loop.html" title="The Main Event Loop">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="glib-Atomic-Operations.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td> </td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GLib Reference Manual</th>
+<td><a accesskey="n" href="glib-The-Main-Event-Loop.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="chapter">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="glib-core"></a>GLib Core Application Support</h2></div></div></div>
+<div class="toc"><dl>
+<dt>
+<span class="refentrytitle"><a href="glib-The-Main-Event-Loop.html">The Main Event Loop</a></span><span class="refpurpose"> — manages all available sources of events</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Threads.html">Threads</a></span><span class="refpurpose"> — thread abstraction; including threads, different
+                    mutexes, conditions and thread private data</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Thread-Pools.html">Thread Pools</a></span><span class="refpurpose"> — pools of threads to execute work concurrently</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Asynchronous-Queues.html">Asynchronous Queues</a></span><span class="refpurpose"> — asynchronous communication between threads</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Dynamic-Loading-of-Modules.html">Dynamic Loading of Modules</a></span><span class="refpurpose"> — portable method for dynamically loading 'plug-ins'</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Memory-Allocation.html">Memory Allocation</a></span><span class="refpurpose"> — general memory-handling</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-IO-Channels.html">IO Channels</a></span><span class="refpurpose"> — portable support for using files, pipes and
+                    sockets</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Error-Reporting.html">Error Reporting</a></span><span class="refpurpose"> — a system for reporting errors</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Warnings-and-Assertions.html">Message Output and Debugging Functions</a></span><span class="refpurpose"> — functions to output messages and help debug applications</span>
+</dt>
+<dt>
+<span class="refentrytitle"><a href="glib-Message-Logging.html">Message Logging</a></span><span class="refpurpose"> — versatile support for logging messages with different levels of importance</span>
+</dt>
+</dl></div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/glib/glib-cross-compiling.html ADDED

@@ -0,0 +1,160 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Cross-compiling the GLib package</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GLib Reference Manual">
+<link rel="up" href="glib.html" title="GLib Overview">
+<link rel="prev" href="glib-building.html" title="Compiling the GLib package">
+<link rel="next" href="glib-compiling.html" title="Compiling GLib Applications">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="glib-building.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="glib.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GLib Reference Manual</th>
+<td><a accesskey="n" href="glib-compiling.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="refentry">
+<a name="glib-cross-compiling"></a><div class="titlepage"></div>
+<div class="refnamediv"><table width="100%"><tr>
+<td valign="top">
+<h2><span class="refentrytitle">Cross-compiling the GLib package</span></h2>
+<p>Cross-compiling the GLib Package —
+How to cross-compile GLib
+</p>
+</td>
+<td valign="top" align="right"></td>
+</tr></table></div>
+<div class="refsect1">
+<a name="cross"></a><h2>Building the Library for a different architecture</h2>
+<p>
+        Cross-compilation is the process of compiling a program or
+        library on a different architecture or operating system then
+        it will be run upon. GLib is slightly more difficult to
+        cross-compile than many packages because much of GLib is
+        about hiding differences between different systems.
+      </p>
+<p>
+        These notes cover things specific to cross-compiling GLib;
+        for general information about cross-compilation, see the
+        <span class="application">autoconf</span> info pages.
+      </p>
+<p>
+        GLib tries to detect as much information as possible about
+        the target system by compiling and linking programs without
+        actually running anything; however, some information GLib
+        needs is not available this way. This information needs
+        to be provided to the configure script via a "cache file"
+        or by setting the cache variables in your environment.
+      </p>
+<p>
+        As an example of using a cache file, to cross compile for
+        the "MingW32" Win32 runtine environment on a Linux system,
+        create a file 'win32.cache' with the following contents:
+      </p>
+<pre class="programlisting">
+glib_cv_long_long_format=I64
+glib_cv_stack_grows=no
+      </pre>
+<p>
+        Then execute the following commands:
+      </p>
+<pre class="programlisting">
+PATH=/path/to/mingw32-compiler/bin:$PATH
+chmod a-w win32.cache   # prevent configure from changing it
+./configure --cache-file=win32.cache --host=mingw32
+      </pre>
+<p>
+        The complete list of cache file variables follows. Most
+         of these won't need to be set in most cases.
+      </p>
+</div>
+<div class="refsect1">
+<a name="cache-file-variables"></a><h2>Cache file variables</h2>
+<p><b>glib_cv_long_long_format=[ll/q/I64]. </b>
+           Format used by <code class="function">printf()</code> and
+           <code class="function">scanf()</code> for 64 bit integers. "ll" is
+           the C99 standard, and what is used by the 'trio' library
+           that GLib builds if your <code class="function">printf()</code> is
+           insufficiently capable.
+           Doesn't need to be set if you are compiling using trio.
+        </p>
+<p><b>glib_cv_stack_grows=[yes/no]. </b>
+           Whether the stack grows up or down. Most places will want "no",
+           A few architectures, such as PA-RISC need "yes".
+        </p>
+<p><b>glib_cv_working_bcopy=[yes/no]. </b>
+           Whether your <code class="function">bcopy()</code> can handle overlapping
+           copies. Only needs to be set if you don't have
+           <code class="function">memmove()</code>. (Very unlikely)
+	</p>
+<p><b>glib_cv_sane_realloc=[yes/np]. </b>
+            Whether your <code class="function">realloc()</code> conforms to ANSI C
+            and can handle <code class="literal">NULL</code> as the first argument.
+            Defaults to "yes" and probably doesn't need to be set.
+	</p>
+<p><b>glib_cv_have_strlcpy=[yes/no]. </b>
+            Whether you have <code class="function">strlcpy()</code> that matches
+            OpenBSD. Defaults to "no", which is safe, since GLib uses a
+            built-in version in that case.
+	</p>
+<p><b>glib_cv_va_val_copy=[yes/no]. </b>
+            Whether <span class="type">va_list</span> can be copied as a pointer. If set
+            to "no", then <code class="function">memcopy()</code> will be used. Only
+            matters if you don't have <code class="function">va_copy()</code> or
+            <code class="function">__va_copy()</code>. (So, doesn't matter for GCC.)
+            Defaults to "yes" which is slightly more common than "no".
+	</p>
+<p><b>glib_cv_rtldglobal_broken=[yes/no]. </b>
+            Whether you have a bug found in OSF/1 v5.0. Defaults to "no".
+         </p>
+<p><b>glib_cv_uscore=[yes/no]. </b>
+            Whether an underscore needs to be prepended to symbols when
+            looking them up via <code class="function">dlsym()</code>. Only needs to
+            be set if your system uses
+	    <code class="function">dlopen()</code>/<code class="function">dlsym()</code>.
+	 </p>
+<p><b>ac_cv_func_posix_getpwuid_r=[yes/no]. </b>
+            Whether you have a getpwuid_r function (in your C library,
+	    not your thread library) that conforms to the POSIX spec.
+            (Takes a 'struct passwd **' as the final argument)
+         </p>
+<p><b>ac_cv_func_nonposix_getpwuid_r=[yes/no]. </b>
+            Whether you have some variant of <code class="function">getpwuid_r()</code>
+            that doesn't conform to to the POSIX spec, but GLib might be able
+            to use (or might segfault.) Only needs to be set if
+	    <code class="literal">ac_cv_func_posix_getpwuid_r</code> is not set. It's
+            safest to set this to "no".
+         </p>
+<p><b>ac_cv_func_posix_getgrgid_r=[yes/no]. </b>
+            Whether you have a getgrgid_r function that conforms to
+            the POSIX spec.
+         </p>
+<p><b>glib_cv_use_pid_surrogate=[yes/no]. </b>
+            Whether to use a <code class="function">setpriority()</code> on the PID of
+            the thread as a method for setting the priority of threads. This
+            only needs to be set when using POSIX threads.
+         </p>
+<p><b>ac_cv_func_printf_unix98=[yes/no]. </b>
+           Whether your <code class="function">printf()</code> family supports Unix98
+           style <code class="literal">%N$</code> positional parameters. Defaults to
+	"no".
+         </p>
+<p><b>ac_cv_func_vsnprintf_c99=[yes/no]. </b>
+            Whether you have a <code class="function">vsnprintf()</code> with C99
+            semantics. (C99 semantics means returning the number of bytes
+            that would have been written had the output buffer had enough
+            space.) Defaults to "no".
+         </p>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>