autobook_14.html

Autoconf使用手册

<DT><SAMP>`--sbindir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies the location of installed superuser binary files.  These are
programs which are usually only run by the superuser.
<P>

<DT><SAMP>`--libexecdir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies the location of installed executable support files.
Contrasted with `binary files', these files are never run directly by
users, but may be executed by the binary files mentioned above.
<P>

<DT><SAMP>`--datadir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies the location of generic data files.
<P>

<DT><SAMP>`--sysconfdir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies the location of read-only data used on a single machine.
<P>

<DT><SAMP>`--sharedstatedir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies the location of data which may be modified, and which may be
shared across several machines.
<P>

<DT><SAMP>`--localstatedir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies the location of data which may be modified, but which is
specific to a single machine.
<P>

<DT><SAMP>`--libdir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies where object code library should be installed.
<P>

<DT><SAMP>`--includedir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies where C header files should be installed.  Header files for
other languages such as C++ may be installed here also.
<P>

<DT><SAMP>`--oldincludedir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies where C header files should be installed for compilers other
than GCC.
<P>

<DT><SAMP>`--infodir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies where Info format documentation files should be installed.
Info is the documentation format used by the GNU project.
<P>

<DT><SAMP>`--mandir=<VAR>dir</VAR>'</SAMP>
<DD>Specifies where manual pages should be installed.
<P>

<DT><SAMP>`--srcdir=<VAR>dir</VAR>'</SAMP>
<DD>This option does not affect installation.  Instead, it tells
<TT>`configure'</TT> where the source files may be found.  It is normally
not necessary to specify this, since the configure script is normally in
the same directory as the source files.
<P>

<DT><SAMP>`--program-prefix=<VAR>prefix</VAR>'</SAMP>
<DD>Specifies a prefix which should be added to the name of a program when
installing it.  For example, using <SAMP>`--program-prefix=g'</SAMP> when
configuring a program normally named <TT>`tar'</TT> will cause the installed
program to be named <TT>`gtar'</TT> instead.  As with the other installation
options, this <TT>`configure'</TT> option only works if it is utilized by
the <TT>`Makefile.in'</TT> file.
<P>

<DT><SAMP>`--program-suffix=<VAR>suffix</VAR>'</SAMP>
<DD>Specifies a suffix which should be appended to the name of a program
when installing it.
<P>

<DT><SAMP>`--program-transform-name=<VAR>program</VAR>'</SAMP>
<DD>Here, <VAR>program</VAR> is a <CODE>sed</CODE> script.  When a program is
installed, its name will be run through <SAMP>`sed -e <VAR>script</VAR>'</SAMP> to
produce the installed name.
</DL>
<P>

<DL COMPACT>
<DT><SAMP>`--build=<VAR>build</VAR>'</SAMP>
<DD>Specifies the type of system on which the package will be built.  If
not specified, the default will be the same configuration name as the host.
<P>

<DT><SAMP>`--host=<VAR>host</VAR>'</SAMP>
<DD>Specifies the type of system on which the package will run--or <EM>be
hosted</EM>.  If not specified, the host triplet is determined by executing
<TT>`config.guess'</TT>.
<P>

<DT><SAMP>`--target=<VAR>target</VAR>'</SAMP>
<DD>Specifies the type of system which the package is to be targeted to.
This makes the most sense in the context of programming language tools
like compilers and assemblers.  If not specified, the default will be
the same configuration name as the host.
<P>

<DT><SAMP>`--disable-<VAR>feature</VAR>'</SAMP>
<DD>Some packages may choose to provide compile-time configurability for
large-scale options such as using the Kerberos authentication system or
an experimental compiler optimization pass.  If the default is to
provide such features, they may be disabled with
<SAMP>`--disable-<VAR>feature</VAR>'</SAMP>, where <VAR>feature</VAR> is the feature's
designated name.  For example:
<P>

<TABLE><tr><td>&nbsp;</td><td class=smallexample><FONT SIZE=-1><pre>$ ./configure --disable-gui
</FONT></pre></td></tr></table></P><P>

<DT><SAMP>`--enable-<VAR>feature</VAR>[=<VAR>arg</VAR>]'</SAMP>
<DD>Conversely, some packages may provide features which are disabled by
default.  To enable them, use <SAMP>`--enable-<VAR>feature</VAR>'</SAMP>, where
<VAR>feature</VAR> is the feature's designated name.  A feature may accept an
optional argument.  For example:
<P>

<TABLE><tr><td>&nbsp;</td><td class=smallexample><FONT SIZE=-1><pre>	$ ./configure --enable-buffers=128
</FONT></pre></td></tr></table></P><P>

Using <SAMP>`--enable-<VAR>feature</VAR>=no'</SAMP> is synonymous with
<SAMP>`--disable-<VAR>feature</VAR>'</SAMP>, described above.
</P><P>

<DT><SAMP>`--with-<VAR>package</VAR>[=<VAR>arg</VAR>]'</SAMP>
<DD>In the free software community, there is a healthy tendency to reuse
existing packages and libraries where possible.  At the time when a
source tree is configured by <TT>`configure'</TT>, it is possible to
provide hints about other installed packages.  For example, the BLT
widget toolkit relies on Tcl and Tk.  To configure BLT, it may be
necessary to give <TT>`configure'</TT> some hints about where you have
installed Tcl and Tk:
<P>

<TABLE><tr><td>&nbsp;</td><td class=smallexample><FONT SIZE=-1><pre>	$ ./configure --with-tcl=/usr/local --with-tk=/usr/local
</FONT></pre></td></tr></table></P><P>

Using <SAMP>`--with-<VAR>package</VAR>=no'</SAMP> is synonymous with
<SAMP>`--without-<VAR>package</VAR>'</SAMP> which is described below.
</P><P>

<DT><SAMP>`--without-<VAR>package</VAR>'</SAMP>
<DD>Sometimes you may not want your package to inter-operate with some
pre-existing package installed on your system.  For example, you might
not want your new compiler to use GNU <CODE>ld</CODE>.  You can prevent
this by using an option such as:
<P>

<TABLE><tr><td>&nbsp;</td><td class=smallexample><FONT SIZE=-1><pre>	$ ./configure --without-gnu-ld
</FONT></pre></td></tr></table></P><P>

<DT><SAMP>`--x-includes=<VAR>dir</VAR>'</SAMP>
<DD>This option is really a specific instance of a <SAMP>`--with-package'</SAMP>
option.  At the time when Autoconf was initially being developed, it was
common to use <TT>`configure'</TT> to build programs to run on the X Window
System as an alternative to Imake.  The <SAMP>`--x-includes'</SAMP> option
provides a way to guide the configure script to the directory containing
the X11 header files.
<P>

<DT><SAMP>`--x-libraries=<VAR>dir</VAR>'</SAMP>
<DD>Similarly, the --x-libraries option provides a way to guide
<TT>`configure'</TT> to the directory containing the X11 libraries.
</DL>
<P>

It is unnecessary, and often undesirable, to run <TT>`configure'</TT> from
within the source tree.  Instead, a well-written <TT>`Makefile'</TT>
generated by <TT>`configure'</TT> will be able to build packages whose
source files reside in another tree.  The advantages of building derived
files in a separate tree to the source code are fairly obvious: the
derived files, such as object files, would clutter the source tree.
This would also make it impossible to build those same object files on a
different system or with a different configuration.  Instead, it is
recommended to use three trees: a source tree, a build tree and an
<EM>install tree</EM>.  Here is a closing example of how to build the
GNU malloc package in this way:
</P><P>

<TABLE width=100%><tr><td>&nbsp;</td><td class=example bgcolor=#6688aa><br><pre>  $ gtar zxf mmalloc-1.0.tar.gz
  $ mkdir build &#38;&#38; cd build
  $ ../mmalloc-1.0/configure
  creating cache ./config.cache
  checking for gcc... gcc
  checking whether the C compiler (gcc  ) works... yes
  checking whether the C compiler (gcc  ) is a cross-compiler... no
  checking whether we are using GNU C... yes
  checking whether gcc accepts -g... yes
  checking for a BSD compatible install... /usr/bin/install -c
  checking host system type... i586-pc-linux-gnu
  checking build system type... i586-pc-linux-gnu
  checking for ar... ar
  checking for ranlib... ranlib
  checking how to run the C preprocessor... gcc -E
  checking for unistd.h... yes
  checking for getpagesize... yes
  checking for working mmap... yes
  checking for limits.h... yes
  checking for stddef.h... yes
  updating cache ../config.cache
  creating ./config.status
</pre></td></tr></table></P><P>

Now that this build tree is configured, it is possible to go on and
build the package and install it into the default location of
<TT>`/usr/local'</TT>:
</P><P>

<TABLE><tr><td>&nbsp;</td><td class=smallexample><FONT SIZE=-1><pre>  $ make all &#38;&#38; make install
</FONT></pre></td></tr></table></P><P>

<A NAME="Files generated by configure"></A>
</TR></TABLE>
<BR>  
<FONT SIZE="-1">
This document was generated
by <I>Gary V. Vaughan</I> on <I>September, 12  2004</I>
using <A HREF="http://www.mathematik.uni-kl.de/~obachman/Texi2html
"><I>texi2html</I></A>

</BODY>
</HTML>