source: trunk/mondo/INSTALL @ 171

Last change on this file since 171 was 129, checked in by bcornec, 14 years ago

Removal of the code related to Xmondo/X11/KDE

  • Property svn:keywords set to Id
File size: 7.3 KB
Line 
1Basic Installation
2==================
3
4gzip -dc mondo-x.xx.tar.gz | tar -xvf-
5cd mondo-x.xx
6./configure <args-to-configure>
7make
8make install
9
10<args-to-configure> can be blank if your needs are simple. If not, read
11configure --help. Example: use --prefix=/usr to install in /usr instead
12of /usr/local. If you have extreme needs and 50 media isn't enough,
13configure --with-maximum-noof-media=<big-number>. To make a statically
14linked mondorestore (not tested), configure --enable-static-mr.
15
16
17[original entry]
18
19   These are generic installation instructions.
20
21   The `configure' shell script attempts to guess correct values for
22various system-dependent variables used during compilation.  It uses
23those values to create a `Makefile' in each directory of the package.
24It may also create one or more `.h' files containing system-dependent
25definitions.  Finally, it creates a shell script `config.status' that
26you can run in the future to recreate the current configuration, a file
27`config.cache' that saves the results of its tests to speed up
28reconfiguring, and a file `config.log' containing compiler output
29(useful mainly for debugging `configure').
30
31   If you need to do unusual things to compile the package, please try
32to figure out how `configure' could check whether to do them, and mail
33diffs or instructions to the address given in the `README' so they can
34be considered for the next release.  If at some point `config.cache'
35contains results you don't want to keep, you may remove or edit it.
36
37   The file `configure.in' is used to create `configure' by a program
38called `autoconf'.  You only need `configure.in' if you want to change
39it or regenerate `configure' using a newer version of `autoconf'.
40
41The simplest way to compile this package is:
42
43  1. `cd' to the directory containing the package's source code and type
44     `./configure' to configure the package for your system.  If you're
45     using `csh' on an old version of System V, you might need to type
46     `sh ./configure' instead to prevent `csh' from trying to execute
47     `configure' itself.
48
49     Running `configure' takes a while.  While running, it prints some
50     messages telling which features it is checking for.
51
52  2. Type `make' to compile the package.
53
54  3. Type `make install' to install the programs and any data files and
55     documentation.
56
57  4. You can remove the program binaries and object files from the
58     source code directory by typing `make clean'. 
59
60Compilers and Options
61=====================
62
63   Some systems require unusual options for compilation or linking that
64the `configure' script does not know about.  You can give `configure'
65initial values for variables by setting them in the environment.  Using
66a Bourne-compatible shell, you can do that on the command line like
67this:
68     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
69
70Or on systems that have the `env' program, you can do it like this:
71     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
72
73Compiling For Multiple Architectures
74====================================
75
76   You can compile the package for more than one kind of computer at the
77same time, by placing the object files for each architecture in their
78own directory.  To do this, you must use a version of `make' that
79supports the `VPATH' variable, such as GNU `make'.  `cd' to the
80directory where you want the object files and executables to go and run
81the `configure' script.  `configure' automatically checks for the
82source code in the directory that `configure' is in and in `..'.
83
84   If you have to use a `make' that does not supports the `VPATH'
85variable, you have to compile the package for one architecture at a time
86in the source code directory.  After you have installed the package for
87one architecture, use `make distclean' before reconfiguring for another
88architecture.
89
90Installation Names
91==================
92
93   By default, `make install' will install the package's files in
94`/usr/local/bin', `/usr/local/man', etc.  You can specify an
95installation prefix other than `/usr/local' by giving `configure' the
96option `--prefix=PATH'.
97
98   You can specify separate installation prefixes for
99architecture-specific files and architecture-independent files.  If you
100give `configure' the option `--exec-prefix=PATH', the package will use
101PATH as the prefix for installing programs and libraries.
102Documentation and other data files will still use the regular prefix.
103
104   If the package supports it, you can cause programs to be installed
105with an extra prefix or suffix on their names by giving `configure' the
106option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
107
108Optional Features
109=================
110
111   Some packages pay attention to `--enable-FEATURE' options to
112`configure', where FEATURE indicates an optional part of the package.
113They may also pay attention to `--with-PACKAGE' options, where PACKAGE
114is something like `gnu-as' or `x' (for the X Window System).  The
115`README' should mention any `--enable-' and `--with-' options that the
116package recognizes.
117
118   For packages that use the X Window System, `configure' can usually
119find the X include and library files automatically, but if it doesn't,
120you can use the `configure' options `--x-includes=DIR' and
121`--x-libraries=DIR' to specify their locations.
122
123Specifying the System Type
124==========================
125
126   There may be some features `configure' can not figure out
127automatically, but needs to determine by the type of host the package
128will run on.  Usually `configure' can figure that out, but if it prints
129a message saying it can not guess the host type, give it the
130`--host=TYPE' option.  TYPE can either be a short name for the system
131type, such as `sun4', or a canonical name with three fields:
132     CPU-COMPANY-SYSTEM
133
134See the file `config.sub' for the possible values of each field.  If
135`config.sub' isn't included in this package, then this package doesn't
136need to know the host type.
137
138   If you are building compiler tools for cross-compiling, you can also
139use the `--target=TYPE' option to select the type of system they will
140produce code for and the `--build=TYPE' option to select the type of
141system on which you are compiling the package.
142
143Sharing Defaults
144================
145
146   If you want to set default values for `configure' scripts to share,
147you can create a site shell script called `config.site' that gives
148default values for variables like `CC', `cache_file', and `prefix'.
149`configure' looks for `PREFIX/share/config.site' if it exists, then
150`PREFIX/etc/config.site' if it exists.  Or, you can set the
151`CONFIG_SITE' environment variable to the location of the site script.
152A warning: not all `configure' scripts look for a site script.
153
154Operation Controls
155==================
156
157   `configure' recognizes the following options to control how it
158operates.
159
160`--cache-file=FILE'
161     Use and save the results of the tests in FILE instead of
162     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
163     debugging `configure'.
164
165`--help'
166     Print a summary of the options to `configure', and exit.
167
168`--quiet'
169`--silent'
170`-q'
171     Do not print messages saying which checks are being made.
172
173`--srcdir=DIR'
174     Look for the package's source code in directory DIR.  Usually
175     `configure' can determine that directory automatically.
176
177`--version'
178     Print the version of Autoconf used to generate the `configure'
179     script, and exit.
180
181`configure' also accepts some other, not widely useful, options.
182
Note: See TracBrowser for help on using the repository browser.