source: branches/3.0/mondo/INSTALL @ 3080

Last change on this file since 3080 was 30, checked in by bcornec, 14 years ago

Id property added on files to allow for better conf. management

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