gtk-building.html

最新gtk中文资料集

	  the <a class="ulink" href="ftp://ftp.gtk.org/pub/gtk/v2.6/" target="_top">GTK+ FTP
	  site.</a>. 
	</p></li>
<li><p>
	  ATK is the Accessibility Toolkit. It provides a set of generic
	  interfaces allowing accessibility technologies such as
	  screen readers to interact with a graphical user interface.
	  It is available from the <a class="ulink" href="ftp://ftp.gtk.org/pub/gtk/v2.6/" target="_top">GTK+ FTP site.</a>
	</p></li>
<li><p>
	  The <a class="ulink" href="http://www.gnu.org/software/libiconv/" target="_top">GNU
	  libiconv library</a> is needed to build GLib if your
	  system doesn't have the <code class="function">iconv()</code>
	  function for doing conversion between character
	  encodings. Most modern systems should have
	  <code class="function">iconv()</code>.
	</p></li>
<li><p>
	  The libintl library from the <a class="ulink" href="http://www.gnu.org/software/gettext/" target="_top">GNU gettext
	  package</a> is needed if your system doesn't have the
	  <code class="function">gettext()</code> functionality for handling
	  message translation databases.
	</p></li>
<li><p>
	  The <a class="ulink" href="ftp://ftp.uu.net/graphics/jpeg/" target="_top">JPEG</a>,
	  <a class="ulink" href="http://www.libpng.org" target="_top">PNG</a>, and
	  <a class="ulink" href="http://www.libtiff.org" target="_top">TIFF</a> image 
          loading libraries are needed to compile GTK+. You probably 
          already have these libraries installed, but if not, the 
          versions you need are available in the 
           <code class="filename">dependencies</code> directory on the the
	  <a class="ulink" href="ftp://ftp.gtk.org/pub/gtk/v2.6/dependencies/" target="_top">GTK+
	    FTP site.</a>. (Before installing these libraries
	  from source, you should check if your operating system
	  vendor has prebuilt packages of these libraries that you
	  don't have installed.)
	</p></li>
<li><p>
	  The libraries from the X window system are needed to build
	  Pango and GTK+. You should already have these installed on
	  your system, but it's possible that you'll need to install
	  the development environment for these libraries that your
	  operating system vendor provides.
	</p></li>
<li><p>
	  The <a class="ulink" href="http://www.fontconfig.org" target="_top">fontconfig</a>
	  library provides Pango with a standard way of locating
	  fonts and matching them against font names. 
	</p></li>
<li><p>
	  <a class="ulink" href="http://www.cairographics.org" target="_top">Cairo</a>
          is a graphics library that supports vector graphics and image 
          compositing. Both Pango and GTK+ use cairo for much of their
          drawing.
        </p></li>
</ul></div>
</div>
<div class="refsect1" lang="en">
<a name="building"></a><h2>Building and testing GTK+</h2>
<p>
      First make sure that you have the necessary external
      dependencies installed: <span class="command"><strong>pkg-config</strong></span>, GNU make,
      the JPEG, PNG, and TIFF libraries, FreeType, and, if necessary,
      libiconv and libintl. To get detailed information about building 
      these packages, see the documentation provided with the
      individual packages.
      On a Linux system, it's quite likely you'll have all of these
      installed already except for <span class="command"><strong>pkg-config</strong></span>.
    </p>
<p>
      Then build and install the GTK+ libraries in the order:
      GLib, Pango, ATK, then GTK+. For each library, follow the
      steps of <code class="literal">configure</code>, <code class="literal">make</code>,
      <code class="literal">make install</code> mentioned above. If you're
      lucky, this will all go smoothly, and you'll be ready to
      <a class="link" href="gtk-compiling.html" title="Compiling GTK+ Applications">start compiling your own GTK+
	applications</a>. You can test your GTK+ installation
      by running the <span class="command"><strong>gtk-demo</strong></span> program that
      GTK+ installs.
    </p>
<p>
      If one of the <code class="filename">configure</code> scripts fails or running
      <span class="command"><strong>make</strong></span> fails, look closely at the error
      messages printed; these will often provide useful information
      as to what went wrong. When <code class="filename">configure</code>
      fails, extra information, such as errors that a test compilation
      ran into, is found in the file <code class="filename">config.log</code>.
      Looking at the last couple of hundred lines in this file will
      frequently make clear what went wrong. If all else fails, you
      can ask for help on the gtk-list mailing list.
      See <a class="xref" href="gtk-resources.html" title="Mailing lists and bug reports"><span class="refentrytitle">Mailing lists and bug reports</span>(3)</a> for more information.
    </p>
</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 class="command"><strong>configure</strong></span> script for the GTK+ library
	supports a number of additional arguments. (Command line
	arguments for the other GTK+ libraries are described in
	the documentation distributed with the those libraries.)

	</p>
<div class="cmdsynopsis"><p><code class="command">configure</code>  [[--disable-modules] |  [--enable-modules]] [[--with-included-loaders==LOADER1,LOADER2,...]] [[--enable-debug=[no|minimum|yes]]] [[--disable-visibility] |  [--enable-visibility]] [[--disable-shm] |  [--enable-shm]] [[--disable-xim] |  [--enable-xim]] [[--disable-xim-inst] |  [--enable-xim-inst]] [[--disable-xkb] |  [--enable-xkb]] [[--disable-xinerama] |  [--enable-xinerama]] [[--disable-gtk-doc] |  [--enable-gtk-doc]] [[--with-xinput=[no|yes]]] [[--with-gdktarget=[x11|win32|quartz|directfb]]]</p></div>
<p>
      </p>
<p><b><code class="systemitem">--disable-modules</code> and
	  <code class="systemitem">--enable-modules</code>.&#160;</b>
	  Normally GTK+ will try to build the GdkPixbuf image file
	  format loaders as little shared libraries that are loaded on
	  demand.  The <code class="systemitem">--disable-modules</code>
	  argument indicates that they should all be built statically
	  into the GTK+ library instead.  This is useful for
	  people who need to produce statically-linked binaries.  If
	  neither <code class="systemitem">--disable-modules</code> nor
	  <code class="systemitem">--enable-modules</code> is specified, then
	  the <span class="command"><strong>configure</strong></span> script will try to
	  auto-detect whether shared modules work on your system.
	</p>
<p><b><code class="systemitem">--with-included-loaders</code>.&#160;</b>
         This option allows you to specify which image loaders you
         want to include; for example, you might include only the PNG
         loader to create a smaller GdkPixbuf binary.
	</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 
         <a class="link" href="gtk-running.html#GTK-Debug-Options" title="GTK_DEBUG">runtime debugging</a>. 
         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 GTK+.
        </p>
<p><b><code class="systemitem">--disable-visibility</code> and
          <code class="systemitem">--enable-visibility</code>.&#160;</b>
          The option <code class="systemitem">--disable-visibility</code>
          turns off the use of ELF visibility attributes for linking
          optimizations. This makes sense while changing GTK+ itself,
          since the way in which GTK+ uses visibility attributes 
          forces a full rebuild of all source files for any header
          modification.
        </p>
<p><b><code class="systemitem">--enable-explicit-deps</code> and
          <code class="systemitem">--disable-explicit-deps</code>.&#160;</b>
	  If <code class="systemitem">--enable-explicit-deps</code> is
	  specified then GTK+ will write the full set of libraries
	  that GTK+ depends upon into its <code class="literal">.pc</code> files to be used when
	  programs depending on GTK+ are linked. Otherwise, GTK+
	  only will include the GTK+ libraries themselves, and
	  will depend on system library dependency facilities to
	  bring in the other libraries.
	  By default GTK+ will disable explicit dependencies unless
	  it detects that they are needed on the system. (If you
	  specify <code class="systemitem">--enable-static</code> to force
	  building of static libraries, then explicit dependencies
	  will be written since library dependencies don't work
	  for static libraries.) Specifying
	  <code class="systemitem">--enable-explicit-deps</code> or
	  <code class="systemitem">--enable-static</code> can cause
	  compatibility
	  problems when libraries that GTK+ depends upon change
	  their versions, and should be avoided if possible.
        </p>
<p><b><code class="systemitem">--disable-shm</code> and
          <code class="systemitem">--enable-shm</code>.&#160;</b>
          These options can be used to control whether GTK+ will use shared 
          memory to communicate with the X server when possible.
          The default is 'yes'.
        </p>
<p><b><code class="systemitem">--disable-xim</code> and
          <code class="systemitem">--enable-xim</code>.&#160;</b>
          These options can be used to control whether GTK+ will 
          be compiled with support for XIM. (The X Input Method
	  extension, used for Japanese input.) The default is yes.
        </p>
<p><b><code class="systemitem">--disable-xim-inst</code> and
          <code class="systemitem">--enable-xim-inst</code>.&#160;</b>
          These options determine whether GTK+ will use the 
	  XIM instantiate callback. 
          The default is 'yes', unless the host system is Solaris,
	  where <code class="function">XRegisterIMInstantiateCallback()</code>
	  seems to cause a segfault.
        </p>
<p><b><code class="systemitem">--disable-xkb</code> and
          <code class="systemitem">--enable-xkb</code>.&#160;</b>
	  By default the <span class="command"><strong>configure</strong></span> script will try
	  to auto-detect whether the XKB extension is supported by
          the X libraries GTK+ is linked with.
          These options can be used to explicitly control whether
	  GTK+ will support the XKB extension. 
        </p>
<p><b><code class="systemitem">--disable-xinerama</code> and
          <code class="systemitem">--enable-xinerama</code>.&#160;</b>
          By default the <span class="command"><strong>configure</strong></span> script will try
          to link against the Xinerama libraries if they are found.
          These options can be used to explicitly control whether
          Xinerama should be used.
        </p>
<p><b><code class="systemitem">--disable-gtk-doc</code> and
	  <code class="systemitem">--enable-gtk-doc</code>.&#160;</b>
	  The <span class="application">gtk-doc</span> package is
	  used to generate the reference documentation included
	  with GTK+. By default support for <span class="application">gtk-doc</span> 
	  is disabled because it requires various extra dependencies
	  to be installed. If you have
	  <span class="application">gtk-doc</span> installed and
	  are modifying GTK+, you may want to enable
	  <span class="application">gtk-doc</span> support by passing
	  in <code class="systemitem">--enable-gtk-doc</code>. If not
	  enabled, pre-generated HTML files distributed with GTK+
	  will be installed.
	</p>
<p><b><code class="systemitem">--with-xinput</code>.&#160;</b>
	  Controls whether GTK+ is built with support for the XInput
	  extension. The XInput extension provides an interface
	  to extended input devices such as graphics tablets.
	  When this support is compiled in, specially written
	  GTK+ programs can get access to subpixel positions,
	  multiple simultaneous input devices, and extra "axes"
	  provided by the device such as pressure and tilt
	  information. This is only known to work well on XFree86
	  systems, though other systems do have this extension.
        </p>
<p><b><code class="systemitem">--with-gdktarget</code>.&#160;</b>
          Toggles between the supported backends for GDK. 
          The default is x11, unless the platform is Windows, in which
	  case the default is win32. Other supported backends are
          the quartz backend for OS X, and the DirectFB backend
          for the Linux framebuffer.
	</p>
</div>
</div>
</body>
</html>