1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/tools/picctldisplaytest/INSTALL Tue Jan 29 22:31:52 2008 +0100
1.3 @@ -0,0 +1,167 @@
1.4 +Basic Installation
1.5 +==================
1.6 +
1.7 + These are generic installation instructions.
1.8 +
1.9 + The `configure' shell script attempts to guess correct values for
1.10 +various system-dependent variables used during compilation. It uses
1.11 +those values to create a `Makefile' in each directory of the package.
1.12 +It may also create one or more `.h' files containing system-dependent
1.13 +definitions. Finally, it creates a shell script `config.status' that
1.14 +you can run in the future to recreate the current configuration, a file
1.15 +`config.cache' that saves the results of its tests to speed up
1.16 +reconfiguring, and a file `config.log' containing compiler output
1.17 +(useful mainly for debugging `configure').
1.18 +
1.19 + If you need to do unusual things to compile the package, please try
1.20 +to figure out how `configure' could check whether to do them, and mail
1.21 +diffs or instructions to the address given in the `README' so they can
1.22 +be considered for the next release. If at some point `config.cache'
1.23 +contains results you don't want to keep, you may remove or edit it.
1.24 +
1.25 + The file `configure.in' is used to create `configure' by a program
1.26 +called `autoconf'. You only need `configure.in' if you want to change
1.27 +it or regenerate `configure' using a newer version of `autoconf'.
1.28 +
1.29 +The simplest way to compile this package is:
1.30 +
1.31 + 1. `cd' to the directory containing the package's source code and type
1.32 + `./configure' to configure the package for your system. If you're
1.33 + using `csh' on an old version of System V, you might need to type
1.34 + `sh ./configure' instead to prevent `csh' from trying to execute
1.35 + `configure' itself.
1.36 +
1.37 + Running `configure' takes a while. While running, it prints some
1.38 + messages telling which features it is checking for.
1.39 +
1.40 + 2. Type `make' to compile the package.
1.41 +
1.42 + 3. Type `make install' to install the programs and any data files and
1.43 + documentation.
1.44 +
1.45 + 4. You can remove the program binaries and object files from the
1.46 + source code directory by typing `make clean'.
1.47 +
1.48 +Compilers and Options
1.49 +=====================
1.50 +
1.51 + Some systems require unusual options for compilation or linking that
1.52 +the `configure' script does not know about. You can give `configure'
1.53 +initial values for variables by setting them in the environment. Using
1.54 +a Bourne-compatible shell, you can do that on the command line like
1.55 +this:
1.56 + CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
1.57 +
1.58 +Or on systems that have the `env' program, you can do it like this:
1.59 + env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
1.60 +
1.61 +Compiling For Multiple Architectures
1.62 +====================================
1.63 +
1.64 + You can compile the package for more than one kind of computer at the
1.65 +same time, by placing the object files for each architecture in their
1.66 +own directory. To do this, you must use a version of `make' that
1.67 +supports the `VPATH' variable, such as GNU `make'. `cd' to the
1.68 +directory where you want the object files and executables to go and run
1.69 +the `configure' script. `configure' automatically checks for the
1.70 +source code in the directory that `configure' is in and in `..'.
1.71 +
1.72 + If you have to use a `make' that does not supports the `VPATH'
1.73 +variable, you have to compile the package for one architecture at a time
1.74 +in the source code directory. After you have installed the package for
1.75 +one architecture, use `make distclean' before reconfiguring for another
1.76 +architecture.
1.77 +
1.78 +Installation Names
1.79 +==================
1.80 +
1.81 + By default, `make install' will install the package's files in
1.82 +`/usr/local/bin', `/usr/local/man', etc. You can specify an
1.83 +installation prefix other than `/usr/local' by giving `configure' the
1.84 +option `--prefix=PATH'.
1.85 +
1.86 + You can specify separate installation prefixes for
1.87 +architecture-specific files and architecture-independent files. If you
1.88 +give `configure' the option `--exec-prefix=PATH', the package will use
1.89 +PATH as the prefix for installing programs and libraries.
1.90 +Documentation and other data files will still use the regular prefix.
1.91 +
1.92 + If the package supports it, you can cause programs to be installed
1.93 +with an extra prefix or suffix on their names by giving `configure' the
1.94 +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
1.95 +
1.96 +Optional Features
1.97 +=================
1.98 +
1.99 + Some packages pay attention to `--enable-FEATURE' options to
1.100 +`configure', where FEATURE indicates an optional part of the package.
1.101 +They may also pay attention to `--with-PACKAGE' options, where PACKAGE
1.102 +is something like `gnu-as' or `x' (for the X Window System). The
1.103 +`README' should mention any `--enable-' and `--with-' options that the
1.104 +package recognizes.
1.105 +
1.106 + For packages that use the X Window System, `configure' can usually
1.107 +find the X include and library files automatically, but if it doesn't,
1.108 +you can use the `configure' options `--x-includes=DIR' and
1.109 +`--x-libraries=DIR' to specify their locations.
1.110 +
1.111 +Specifying the System Type
1.112 +==========================
1.113 +
1.114 + There may be some features `configure' can not figure out
1.115 +automatically, but needs to determine by the type of host the package
1.116 +will run on. Usually `configure' can figure that out, but if it prints
1.117 +a message saying it can not guess the host type, give it the
1.118 +`--host=TYPE' option. TYPE can either be a short name for the system
1.119 +type, such as `sun4', or a canonical name with three fields:
1.120 + CPU-COMPANY-SYSTEM
1.121 +
1.122 +See the file `config.sub' for the possible values of each field. If
1.123 +`config.sub' isn't included in this package, then this package doesn't
1.124 +need to know the host type.
1.125 +
1.126 + If you are building compiler tools for cross-compiling, you can also
1.127 +use the `--target=TYPE' option to select the type of system they will
1.128 +produce code for and the `--build=TYPE' option to select the type of
1.129 +system on which you are compiling the package.
1.130 +
1.131 +Sharing Defaults
1.132 +================
1.133 +
1.134 + If you want to set default values for `configure' scripts to share,
1.135 +you can create a site shell script called `config.site' that gives
1.136 +default values for variables like `CC', `cache_file', and `prefix'.
1.137 +`configure' looks for `PREFIX/share/config.site' if it exists, then
1.138 +`PREFIX/etc/config.site' if it exists. Or, you can set the
1.139 +`CONFIG_SITE' environment variable to the location of the site script.
1.140 +A warning: not all `configure' scripts look for a site script.
1.141 +
1.142 +Operation Controls
1.143 +==================
1.144 +
1.145 + `configure' recognizes the following options to control how it
1.146 +operates.
1.147 +
1.148 +`--cache-file=FILE'
1.149 + Use and save the results of the tests in FILE instead of
1.150 + `./config.cache'. Set FILE to `/dev/null' to disable caching, for
1.151 + debugging `configure'.
1.152 +
1.153 +`--help'
1.154 + Print a summary of the options to `configure', and exit.
1.155 +
1.156 +`--quiet'
1.157 +`--silent'
1.158 +`-q'
1.159 + Do not print messages saying which checks are being made.
1.160 +
1.161 +`--srcdir=DIR'
1.162 + Look for the package's source code in directory DIR. Usually
1.163 + `configure' can determine that directory automatically.
1.164 +
1.165 +`--version'
1.166 + Print the version of Autoconf used to generate the `configure'
1.167 + script, and exit.
1.168 +
1.169 +`configure' also accepts some other, not widely useful, options.
1.170 +