[kaldi]openfst: install script

shaoheshaohe

Briefly, the shell commands `./configure; make; make install' shouldconfigure, build, and install this package.  

The followingmore-detailed instructions are generic; see the `README' file forinstructions specific to this package.  
The `configure' shell script attempts to guess correct values forvarious system-dependent variables used during compilation.  
It usesthose values to create a `Makefile' in each directory of the package.It may also create one or more `.h' files containing system-dependentdefinitions.  
Finally, it creates a shell script `config.status' thatyou can run in the future to recreate the current configuration, and afile `config.log' containing compiler output (useful mainly fordebugging `configure').   

It can also use an optional file (typically called `config.cache'and enabled with `--cache-file=config.cache' or simply `-C') that savesthe results of its tests to speed up reconfiguring.  Caching isdisabled by default to prevent problems with accidental use of stalecache files.   
If you need to do unusual things to compile the package, please tryto figure out how `configure' could check whether to do them, and maildiffs or instructions to the address given in the `README' so they canbe considered for the next release.

If you are using the cache, and atsome point `config.cache' contains results you don't want to keep, youmay remove or edit it.   The file `configure.ac' (or `configure.in') is used to create`configure' by a program called `autoconf'.  You need `configure.ac' ifyou want to change it or regenerate `configure' using a newer versionof `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type   
`./configure'
to configure the package for your system.     
Running `configure' might take a while.  While running, it prints     some messages telling which features it is checking for.  

2. Type `make' to compile the package.  

3. Optionally, type `make check' to run any self-tests that come with     
the package.  

4. Type `make install' to install the programs and any data files and     documentation.

5. You can remove the program binaries and object files from the     source code directory by typing `make clean'.  

To also remove the     files that `configure' created (so you can compile the package for     a different kind of computer), type `make distclean'.  There is     also a `make maintainer-clean' target, but that is intended mainly     for the package's developers.  If you use it, you may have to get     all sorts of other programs in order to regenerate files that came     with the distribution.

6. Often, you can also type `make uninstall' to remove the installed     files again.

----------------------------------------------------------------------------------------------
一般人，看到这里，就行了。下面的都是定制选项。
-----------------------------------------------------------------------------------------------

Compilers and Options=====================
Some systems require unusual options for compilation or linking that the`configure' script does not know about.  Run `./configure --help' fordetails on some of the pertinent environment variables.   You can give `configure' initial values for configuration parametersby setting variables in the command line or in the environment.  Hereis an example:     ./configure CC=c99 CFLAGS=-g LIBS=-lposix   *Note Defining Variables::, for more details.

Compiling For Multiple Architectures====================================
You can compile the package for more than one kind of computer at thesame time, by placing the object files for each architecture in theirown directory.  To do this, you can use GNU `make'.  `cd' to thedirectory where you want the object files and executables to go and runthe `configure' script.  `configure' automatically checks for thesource code in the directory that `configure' is in and in `..'.   With a non-GNU `make', it is safer to compile the package for onearchitecture at a time in the source code directory.  After you haveinstalled the package for one architecture, use `make distclean' beforereconfiguring for another architecture.

Installation Names==================
By default, `make install' installs the package's commands under`/usr/local/bin', include files under `/usr/local/include', etc.  Youcan specify an installation prefix other than `/usr/local' by giving`configure' the option `--prefix=PREFIX'.   You can specify separate installation prefixes forarchitecture-specific files and architecture-independent files.  If youpass the option `--exec-prefix=PREFIX' to `configure', the package usesPREFIX as the prefix for installing programs and libraries.Documentation and other data files still use the regular prefix.   In addition, if you use an unusual directory layout you can giveoptions like `--bindir=DIR' to specify different values for particularkinds of files.  Run `configure --help' for a list of the directoriesyou can set and what kinds of files go in them.   If the package supports it, you can cause programs to be installedwith an extra prefix or suffix on their names by giving `configure' theoption `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features=================

Some packages pay attention to `--enable-FEATURE' options to`configure', where FEATURE indicates an optional part of the package.They may also pay attention to `--with-PACKAGE' options, where PACKAGEis something like `gnu-as' or `x' (for the X Window System).  The`README' should mention any `--enable-' and `--with-' options that thepackage recognizes.   For packages that use the X Window System, `configure' can usuallyfind the X include and library files automatically, but if it doesn't,you can use the `configure' options `--x-includes=DIR' and`--x-libraries=DIR' to specify their locations.

Specifying the System Type==========================

There may be some features `configure' cannot figure out automatically,but needs to determine by the type of machine the package will run on.Usually, assuming the package is built to be run on the _same_architectures, `configure' can figure that out, but if it prints amessage saying it cannot guess the machine type, give it the`--build=TYPE' option.  TYPE can either be a short name for the systemtype, such as `sun4', or a canonical name which has the form:     CPU-COMPANY-SYSTEMwhere SYSTEM can have one of these forms:     OS KERNEL-OS   See the file `config.sub' for the possible values of each field.  If`config.sub' isn't included in this package, then this package doesn'tneed to know the machine type.   If you are _building_ compiler tools for cross-compiling, you shoulduse the option `--target=TYPE' to select the type of system they willproduce code for.   If you want to _use_ a cross compiler, that generates code for aplatform different from the build platform, you should specify the"host" platform (i.e., that on which the generated programs willeventually be run) with `--host=TYPE'.

Sharing Defaults================
If you want to set default values for `configure' scripts to share, youcan create a site shell script called `config.site' that gives defaultvalues for variables like `CC', `cache_file', and `prefix'.`configure' looks for `PREFIX/share/config.site' if it exists, then`PREFIX/etc/config.site' if it exists.  Or, you can set the`CONFIG_SITE' environment variable to the location of the site script.A warning: not all `configure' scripts look for a site script.

Defining Variables==================
Variables not defined in a site shell script can be set in theenvironment passed to `configure'.  However, some packages may runconfigure again during the build, and the customized values of thesevariables may be lost.  In order to avoid this problem, you should setthem in the `configure' command line, using `VAR=value'.  For example:     ./configure CC=/usr/local2/bin/gcccauses the specified `gcc' to be used as the C compiler (unless it isoverridden in the site shell script).Unfortunately, this technique does not work for `CONFIG_SHELL' due toan Autoconf bug.  Until the bug is fixed you can use this workaround:     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash`configure'

Invocation======================
`configure' recognizes the following options to control how it operates.`--help'`-h'     Print a summary of the options to `configure', and exit.`--version'`-V'     Print the version of Autoconf used to generate the `configure'     script, and exit.`--cache-file=FILE'     Enable the cache: use and save the results of the tests in FILE,     traditionally `config.cache'.  FILE defaults to `/dev/null' to     disable caching.`--config-cache'`-C'     Alias for `--cache-file=config.cache'.`--quiet'`--silent'`-q'     
Do not print messages saying which checks are being made.  
To     suppress all normal output, redirect it to `/dev/null' (any error     messages will still be shown).`--srcdir=DIR'     
Look for the package's source code in directory DIR.  Usually     `configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options.  Run`configure --help' for more details.