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