Commit 56ad9eb4 authored by Benjamin Drung's avatar Benjamin Drung

Imported Upstream version 2.3

This diff is collapsed.
Audacious (C) GPL 2005-2009
Authors listed alphabetically, by last name:
George Averill <>
Kieran Clancy <>
Michael Färber <>
Matti Hämäläinen <>
Giacomo Lozito <>
Tomasz Moń <>
William Pitcock <>
Derek Pomery <>
Mohammed Sameer <>
Jonathan Schleifer <>
Stephen Sokolow <>
Ben Tucker <>
Tony Vroon <>
Yoshiki Yazawa <>
Dutch - Tony Vroon
Hungarian - Dvornik László
German - Michael Hanselmann
Matthias Debus
Greek - Kouzinopoulos Haris
Stavros Giannouris
Stathis Kamperis
Italian - Diego Petteno
Japanese - Dai
Finnish - Pauli Virtanen
Matti Hämäläinen
Based on:
BMP - beep media player (C) GPL 2003-2005
Authors alphabetically
Artem Baguinski <>
Edward Brocklesby <>
Chong Kai Xiong <>
Milosz Derezynski <>
David Lau <>
Ole Andre Vadla Ravnaas <>
Michiel Sikkes <>
Patch Authors
Andrei Badea
Peter Behroozi
Bernard Blackham
Oliver Blin
David Le Brun
Tomas Bzatek
Liviu Danicel
Jon Dowland
Artur Frysiak
Sebastian Kapfer
Lukas Koberstein
Dan Korostelev
Oliver Lehmann
Jolan Luff
Mike Lundy
Michael Marineau
Tim-Philipp Muller
Julien Portalier
Andrew Ruder
Olivier Samyn
John Spray
Takashi Iwai
Martijn Vernooij
Thierry Vignaud
Brazilian Portuguese - Philipi Pinto <>
Breton - Thierry Vignaud <>
Czech - Jan Narovec <>
Dutch - Laurens Buhler <>
German - Matthias Debus <>
Georgian - George Machitidze <>
Greek - Kouzinopoulos Haris <>
Stavros Giannouris <>
Finnish - Pauli Virtanen <>
French - David Le Brun <>
Hindi - Dhananjaya Sharma <>
Hungarian - Dvornik László <>
Italian - Alessio D'Ascanio <>
Japanese - Takeshi Aihana <>
Korean - DongCheon Park <>
Lithuanian - Rimas Kudelis <>
Macedonian - Arangel Angov <>
Polish - Jacek Wolszczak <>
Romanian - Liviu Danicel <>
Russian - Pavlo Bohmat <>
Dan Korostelev <>
Vitaly Lipatov <>
Simplified Chinese - Chong Kai Xiong <>
Traditional Chinese - Chao-Hsiung Liao <>
Slovak - Pavel Kanzelsberger <>
Spanish - Francisco Javier F. Serrador <>
Swedish - Martin Persenius <>
Ukrainian - Mykola Lynnyk<>
Welsh - Edward Brocklesby <>
(Based on XMMS from Rhoslyn Prys <>)
(please tell us if we left your name out)
Based on:
XMMS - X Multimedia System (C)1998-2003
Main Programming: Peter Alm
Additional Programming: Håvard Kvålen
Derrik Pates
With Additional Help: Sean Atkinson
Jorn Baayen
James M. Cape
Anders Carlsson (effect plugins)
Chun-Chung Chen (xfont patch)
Tim Ferguson (joystick plugin)
Ben Gertzfield
Vesa Halttunen
Logan Hanks
Eric L. Hernes (FreeBSD patches)
Ville Herva
higway (MMX)
Michael Hipp and others (MPG123 engine)
Olle Hällnäs (compiling fixes)
David Jacoby
Osamu Kayasono (3DNow!)
Lyle B Kempler
J. Nick Koston (MikMod plugin)
Aaron Lehmann
Johan Levin (echo + stereo plugin)
Eric Lindvall
Colin Marquardt
Willem Monsuwe
John Riddoch (Solaris plugin)
Josip Rodin
Pablo Saratxaga (i18n)
Carl van Schaik (pro logic plugin)
Jörg Schuler
Charles Sielski (irman plugin)
Espen Skoglund
Matthieu Sozeau (ALSA plugin)
Kimura Takuhiro (3DNow!)
Zinx Verituse
Ryan Weaver (RPMs among other things)
Chris Wilson
Dave Yearke
Stephan K. Zitz
Default skin: Leonard "Blayde" Tan
Robin Sylvestre (Equalizer and Playlist)
Thomas Nilsson (New titles, and cleanups)
Homepage and Graphics: Thomas Nilsson
Support and Docs: Olle Hällnäs
This diff is collapsed.
This diff is collapsed.
Installation Instructions
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `' (or `') is used to create
`configure' by a program called `autoconf'. You only need
`' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
`configure' recognizes the following options to control how it operates.
Print a summary of the options to `configure', and exit.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
Alias for `--cache-file=config.cache'.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
SUBDIRS = src man pixmaps po
for i in audacious.pc audclient.pc; do \
if ${MKDIR_P} ${DESTDIR}${libdir}/pkgconfig && ${INSTALL} -m 644 $$i ${DESTDIR}${libdir}/pkgconfig/$$i; then \
else \
fi; \
for i in audacious2.desktop audacious2-gtkui.desktop; do \
if ${MKDIR_P} ${DESTDIR}${datadir}/applications && ${INSTALL} -m 644 $$i ${DESTDIR}${datadir}/applications/$$i; then \
else \
fi \
if [ -f ${DESTDIR}${datadir}/audacious/Skins/Default/balance.png ]; then \
rm -f ${DESTDIR}${datadir}/audacious/Skins/Default/balance.png; \
for i in audacious.pc audclient.pc; do \
if [ -f ${DESTDIR}${libdir}/pkgconfig/$$i ]; then \
if rm -f ${DESTDIR}${libdir}/pkgconfig/$$i; then \
else \
fi \
fi; \
for i in audacious2.desktop audacious2-gtkui.desktop; do \
if test -f ${DESTDIR}${datadir}/applications/$$i; then \
if rm -f ${DESTDIR}${datadir}/applications/$$i; then \
else \
fi \
fi \
The mercurial repository is available for anonymous read-only
To retrieve the audacious development branch from, do:
$ hg clone audacious-devel
To retrieve the audacious stable branch from, do:
$ hg clone$VERSION/
Where $VERSION is the stable major version, for example the latest
fixes and updates to 1.5-series of audacious would be in:
$ hg clone
This diff is collapsed.
This diff is collapsed.
dnl ** ADD_PKG_REQUIRES([requirement])
dnl ** Adds a dependency to package's pkg-config file.
if test "x$PC_REQUIRES" = "x"; then
dnl ** AUD_CHECK_MODULE([define name], [module], [version required],
dnl ** [informational name], [additional error message])
dnl **
dnl ** Works like PKG_CHECK_MODULES, but provides an informative
dnl ** error message if the package is not found. NOTICE! Unlike
dnl ** PKG_C_M, this macro ONLY supports one module name!
dnl **
dnl ** AUD_CHECK_MODULE([GLIB], [gtk+-2.0], [>= 2.8.0], [Gtk+2], [See])
PKG_CHECK_MODULES([$1], [$2 $3], [
cv_pkg_version=`$PKG_CONFIG --modversion "$2" 2>/dev/null`
$4 version $cv_pkg_version was found, but $2 $3 is required.
Cannot find $4! If you are using binary packages based system, check that you
have the corresponding -dev/devel packages installed.
dnl ** AUD_CONDITIONAL([symbol], [variable to test][, value])
dnl ** Simplifying wrapper for AM_CONDITIONAL.
dnl **
dnl ** AUD_CONDITIONAL([FOO], [foo])
[if test "x${$2}" = m4_ifval([$3], ["x$3"],["xyes"]) ; then
dnl ** Simple wrapper for AC_ARG_ENABLE
dnl ** AUD_ARG_ENABLE([name], [default value], [help string], [if enabled], [if disabled])
define([Name], [translit([$1], [./-], [___])])dnl
define([cBasce], [ifelse([$2],[yes],[Disable],[Enable]) $3 (def: ifelse([$2],[yes],[enabled],[disabled]))])dnl
AC_ARG_ENABLE([$1], [AS_HELP_STRING([ifelse([$2],[yes],[--disable-$1],[--enable-$1])], cBasce)],, [enable_[]Name=$2])
if test "x${enable_[]Name}" = "xyes"; then
m4_ifvaln([$4], [$4], [:])dnl
m4_ifvaln([$5], [else $5])dnl
define([Name], [translit([$1], [./-], [___])])dnl
define([cBasce], [ifelse([$2],[yes],[Disable],[Enable]) $3 (def: ifelse([$2],[yes],[enabled],[disabled]))])dnl
AC_ARG_ENABLE([$1], [AS_HELP_STRING([ifelse([$2],[yes],[--disable-$1],[--enable-$1])], cBasce)],, [enable_[]Name=$2])
if test "x${enable_[]Name}" = "xyes"; then
AC_DEFINE([$4], [$5], [$6])
AUD_CONDITIONAL([$4], [enable_$1])
dnl ** Wrapper for cached compilation check
dnl ** AUD_TRY_COMPILE([message], [result variable], [includes], [body], [if ok], [if not ok])
AC_CACHE_CHECK([$1], [$2],
[AC_TRY_COMPILE([$3], [$4], [$2="yes"], [$2="no"])])
if test "x${$2}" = "xyes"; then
m4_ifvaln([$5], [$5], [:])dnl
m4_ifvaln([$6], [else $6])dnl