1 2------------------- 3Ezstream uses the GNU auto-tools to build and install on a variety of systems. 4This file contains detailed instructions about a standard GNU software package 5installation, from autoconf-2.61. 6------------------- 7 8 9 10Installation Instructions 11************************* 12 13Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 142006 Free Software Foundation, Inc. 15 16This file is free documentation; the Free Software Foundation gives 17unlimited permission to copy, distribute and modify it. 18 19Basic Installation 20================== 21 22Briefly, the shell commands `./configure; make; make install' should 23configure, build, and install this package. The following 24more-detailed instructions are generic; see the `README' file for 25instructions specific to this package. 26 27 The `configure' shell script attempts to guess correct values for 28various system-dependent variables used during compilation. It uses 29those values to create a `Makefile' in each directory of the package. 30It may also create one or more `.h' files containing system-dependent 31definitions. Finally, it creates a shell script `config.status' that 32you can run in the future to recreate the current configuration, and a 33file `config.log' containing compiler output (useful mainly for 34debugging `configure'). 35 36 It can also use an optional file (typically called `config.cache' 37and enabled with `--cache-file=config.cache' or simply `-C') that saves 38the results of its tests to speed up reconfiguring. Caching is 39disabled by default to prevent problems with accidental use of stale 40cache files. 41 42 If you need to do unusual things to compile the package, please try 43to figure out how `configure' could check whether to do them, and mail 44diffs or instructions to the address given in the `README' so they can 45be considered for the next release. If you are using the cache, and at 46some point `config.cache' contains results you don't want to keep, you 47may remove or edit it. 48 49 The file `configure.ac' (or `configure.in') is used to create 50`configure' by a program called `autoconf'. You need `configure.ac' if 51you want to change it or regenerate `configure' using a newer version 52of `autoconf'. 53 54The simplest way to compile this package is: 55 56 1. `cd' to the directory containing the package's source code and type 57 `./configure' to configure the package for your system. 58 59 Running `configure' might take a while. While running, it prints 60 some messages telling which features it is checking for. 61 62 2. Type `make' to compile the package. 63 64 3. Optionally, type `make check' to run any self-tests that come with 65 the package. 66 67 4. Type `make install' to install the programs and any data files and 68 documentation. 69 70 5. You can remove the program binaries and object files from the 71 source code directory by typing `make clean'. To also remove the 72 files that `configure' created (so you can compile the package for 73 a different kind of computer), type `make distclean'. There is 74 also a `make maintainer-clean' target, but that is intended mainly 75 for the package's developers. If you use it, you may have to get 76 all sorts of other programs in order to regenerate files that came 77 with the distribution. 78 79Compilers and Options 80===================== 81 82Some systems require unusual options for compilation or linking that the 83`configure' script does not know about. Run `./configure --help' for 84details on some of the pertinent environment variables. 85 86 You can give `configure' initial values for configuration parameters 87by setting variables in the command line or in the environment. Here 88is an example: 89 90 ./configure CC=c99 CFLAGS=-g LIBS=-lposix 91 92 *Note Defining Variables::, for more details. 93 94Compiling For Multiple Architectures 95==================================== 96 97You can compile the package for more than one kind of computer at the 98same time, by placing the object files for each architecture in their 99own directory. To do this, you can use GNU `make'. `cd' to the 100directory where you want the object files and executables to go and run 101the `configure' script. `configure' automatically checks for the 102source code in the directory that `configure' is in and in `..'. 103 104 With a non-GNU `make', it is safer to compile the package for one 105architecture at a time in the source code directory. After you have 106installed the package for one architecture, use `make distclean' before 107reconfiguring for another architecture. 108 109Installation Names 110================== 111 112By default, `make install' installs the package's commands under 113`/usr/local/bin', include files under `/usr/local/include', etc. You 114can specify an installation prefix other than `/usr/local' by giving 115`configure' the option `--prefix=PREFIX'. 116 117 You can specify separate installation prefixes for 118architecture-specific files and architecture-independent files. If you 119pass the option `--exec-prefix=PREFIX' to `configure', the package uses 120PREFIX as the prefix for installing programs and libraries. 121Documentation and other data files still use the regular prefix. 122 123 In addition, if you use an unusual directory layout you can give 124options like `--bindir=DIR' to specify different values for particular 125kinds of files. Run `configure --help' for a list of the directories 126you can set and what kinds of files go in them. 127 128 If the package supports it, you can cause programs to be installed 129with an extra prefix or suffix on their names by giving `configure' the 130option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 131 132Optional Features 133================= 134 135Some packages pay attention to `--enable-FEATURE' options to 136`configure', where FEATURE indicates an optional part of the package. 137They may also pay attention to `--with-PACKAGE' options, where PACKAGE 138is something like `gnu-as' or `x' (for the X Window System). The 139`README' should mention any `--enable-' and `--with-' options that the 140package recognizes. 141 142 For packages that use the X Window System, `configure' can usually 143find the X include and library files automatically, but if it doesn't, 144you can use the `configure' options `--x-includes=DIR' and 145`--x-libraries=DIR' to specify their locations. 146 147Specifying the System Type 148========================== 149 150There may be some features `configure' cannot figure out automatically, 151but needs to determine by the type of machine the package will run on. 152Usually, assuming the package is built to be run on the _same_ 153architectures, `configure' can figure that out, but if it prints a 154message saying it cannot guess the machine type, give it the 155`--build=TYPE' option. TYPE can either be a short name for the system 156type, such as `sun4', or a canonical name which has the form: 157 158 CPU-COMPANY-SYSTEM 159 160where SYSTEM can have one of these forms: 161 162 OS KERNEL-OS 163 164 See the file `config.sub' for the possible values of each field. If 165`config.sub' isn't included in this package, then this package doesn't 166need to know the machine type. 167 168 If you are _building_ compiler tools for cross-compiling, you should 169use the option `--target=TYPE' to select the type of system they will 170produce code for. 171 172 If you want to _use_ a cross compiler, that generates code for a 173platform different from the build platform, you should specify the 174"host" platform (i.e., that on which the generated programs will 175eventually be run) with `--host=TYPE'. 176 177Sharing Defaults 178================ 179 180If you want to set default values for `configure' scripts to share, you 181can create a site shell script called `config.site' that gives default 182values for variables like `CC', `cache_file', and `prefix'. 183`configure' looks for `PREFIX/share/config.site' if it exists, then 184`PREFIX/etc/config.site' if it exists. Or, you can set the 185`CONFIG_SITE' environment variable to the location of the site script. 186A warning: not all `configure' scripts look for a site script. 187 188Defining Variables 189================== 190 191Variables not defined in a site shell script can be set in the 192environment passed to `configure'. However, some packages may run 193configure again during the build, and the customized values of these 194variables may be lost. In order to avoid this problem, you should set 195them in the `configure' command line, using `VAR=value'. For example: 196 197 ./configure CC=/usr/local2/bin/gcc 198 199causes the specified `gcc' to be used as the C compiler (unless it is 200overridden in the site shell script). 201 202Unfortunately, this technique does not work for `CONFIG_SHELL' due to 203an Autoconf bug. Until the bug is fixed you can use this workaround: 204 205 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash 206 207`configure' Invocation 208====================== 209 210`configure' recognizes the following options to control how it operates. 211 212`--help' 213`-h' 214 Print a summary of the options to `configure', and exit. 215 216`--version' 217`-V' 218 Print the version of Autoconf used to generate the `configure' 219 script, and exit. 220 221`--cache-file=FILE' 222 Enable the cache: use and save the results of the tests in FILE, 223 traditionally `config.cache'. FILE defaults to `/dev/null' to 224 disable caching. 225 226`--config-cache' 227`-C' 228 Alias for `--cache-file=config.cache'. 229 230`--quiet' 231`--silent' 232`-q' 233 Do not print messages saying which checks are being made. To 234 suppress all normal output, redirect it to `/dev/null' (any error 235 messages will still be shown). 236 237`--srcdir=DIR' 238 Look for the package's source code in directory DIR. Usually 239 `configure' can determine that directory automatically. 240 241`configure' also accepts some other, not widely useful, options. Run 242`configure --help' for more details. 243 244