glib-building.html

glid编写实例

	  e.g. POSIX threads, DCE threads or Solaris threads. 
	</p></li>
</ul></div>
</div>
<div class="refsect1" lang="en">
<a name="extra-configuration-options"></a><h2>Extra Configuration Options</h2>
<p>
        In addition to the normal options, the
        <span><strong class="command">configure</strong></span> script in the GLib
        library supports these additional arguments:

        </p>
<div class="cmdsynopsis"><p><code class="command">configure</code>  [[--enable-debug=[no|minimum|yes]]] [[--disable-gc-friendly] |  [--enable-gc-friendly]] [[--disable-mem-pools] |  [--enable-mem-pools]] [[--disable-threads] |  [--enable-threads]] [[--with-threads=[none|posix|dce|solaris|win32]]] [[--disable-included-printf] |  [--enable-included-printf]] [[--disable-visibility] |  [--enable-visibility]] [[--disable-gtk-doc] |  [--enable-gtk-doc]] [[--disable-man] |  [--enable-man]]</p></div>
<p>
      </p>
<p><b><code class="systemitem">--enable-debug</code>.&#160;</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
         runtime debugging.
         The default is 'minimum'.
         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>.&#160;</b>
          When enabled all memory freed by the application,
          but retained by GLib for performance reasons
          is set to zero, thus making deployed garbage
          collection or memory profiling tools detect
          unlinked memory correctly. This will make GLib
          slightly slower and is thus disabled by default.
        </p>
<p><b><code class="systemitem">--disable-mem-pools</code> and
          <code class="systemitem">--enable-mem-pools</code>.&#160;</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
        memory pools can be disabled to avoid excessive caching and force
        atomic maintenance of chunks through the <code class="function">g_malloc()</code>
        and <code class="function">g_free()</code> functions. Code currently affected by 
        this:
        </p>
<div class="itemizedlist"><ul type="disc">
<li><p>
         <span class="structname">GList</span>, <span class="structname">GSList</span>,
         <span class="structname">GNode</span>, <span class="structname">GHash</span> 
         allocations. The functions g_list_push_allocator(), 
         g_list_pop_allocator(), g_slist_push_allocator(), 
         g_slist_pop_allocator(), g_node_push_allocator() and 
         g_node_pop_allocator() are not available
        </p></li>
<li><p>
        <span class="structname">GMemChunk</span>s become basically non-effective
        </p></li>
<li><p>
         <span class="structname">GSignal</span> disables all caching (potentially 
         very slow)
        </p></li>
<li><p>
         <span class="structname">GType</span> doesn't honour the 
         <span class="structname">GTypeInfo</span> 
         <em class="structfield"><code>n_preallocs</code></em> field anymore
        </p></li>
<li><p>
         the <span class="structname">GBSearchArray</span> flag 
         <code class="literal">G_BSEARCH_ALIGN_POWER2</code> becomes non-functional
        </p></li>
</ul></div>
<p>
      </p>
<p><b><code class="systemitem">--disable-threads</code> and
          <code class="systemitem">--enable-threads</code>.&#160;</b>
           Do not compile GLib to be multi thread safe. GLib
           will be slightly faster then. This is however not
           recommended, as many programs rely on GLib being
           multi thread safe.
        </p>
<p><b><code class="systemitem">--with-threads</code>.&#160;</b>
          Specify a thread implementation to use.
          </p>
<div class="itemizedlist"><ul type="disc">
<li><p>
                'posix' and 'dce' can be used interchangeable
                to mean the different versions of Posix
                threads. configure tries to find out, which
                one is installed.
              </p></li>
<li><p>
                'solaris' uses the native Solaris thread implementation.
              </p></li>
<li><p>
                'none' means that GLib will be thread safe,
                but does not have a default thread
                implementation. This has to be supplied to
                <code class="function">g_thread_init()</code> by the programmer.
              </p></li>
</ul></div>
<p>

        </p>
<p><b><code class="systemitem">--disable-included-printf</code> and
           <code class="systemitem">--enable-included-printf</code>.&#160;</b>
          By default the <span><strong class="command">configure</strong></span> script will try
          to auto-detect whether the C library provides a suitable set
	  of <code class="function">printf()</code> functions. In detail, 
	  <span><strong class="command">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 <code class="function">printf()</code> 
          family.
          These options can be used to explicitly control whether
          an implementation fo the <code class="function">printf()</code> family
          should be included or not.
        </p>
<p><b><code class="systemitem">--disable-visibility</code> and
           <code class="systemitem">--enable-visibility</code>.&#160;</b>
          By default, GLib uses ELF visibility attributes to optimize
          PLT table entries if the compiler supports ELF visibility
          attributes. A side-effect of the way in which this is currently
          implemented is that any  header change forces a full 
          recompilation, and missing includes may go unnoticed. 
          Therefore, it makes sense to turn this feature off while
          doing GLib development, even if the compiler supports ELF
          visibility attributes. The <code class="option">--disable-visibility</code> 
          option allows to do that.
        </p>
<p><b><code class="systemitem">--disable-gtk-doc</code> and
          <code class="systemitem">--enable-gtk-doc</code>.&#160;</b>
          By default the <span><strong class="command">configure</strong></span> script will try
          to auto-detect whether the
          <span class="application">gtk-doc</span> package is installed.  If
          it is, then it will use it to extract and build the
          documentation for the GLib library.  These options
          can be used to explicitly control whether
          <span class="application">gtk-doc</span> should be
          used or not.  If it is not used, the distributed,
          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>.&#160;</b>
          By default the <span><strong class="command">configure</strong></span> script will try
          to auto-detect whether <span class="application">xsltproc</span> 
          and the necessary Docbook stylesheets are installed.  If
          they are, then it will use them to rebuild the included
          man pages from the XML sources.  These options can be used 
          to explicitly control whether man pages should be rebuilt
          used or not. The distribution includes pre-generated man 
          pages.
        </p>
</div>
</div>
<table class="navigation" width="100%" summary="Navigation footer" cellpadding="2" cellspacing="0"><tr valign="middle">
<td align="left"><a accesskey="p" href="glib.html"><b>&lt;&lt;&#160;GLib Overview</b></a></td>
<td align="right"><a accesskey="n" href="glib-cross-compiling.html"><b>Cross-compiling the GLib package&#160;&gt;&gt;</b></a></td>
</tr></table>
</body>
</html>