You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
315 lines
11 KiB
315 lines
11 KiB
Installing Amarok
|
|
=================
|
|
|
|
In order to compile and install Amarok on your system, type the following in the
|
|
base directory of the Amarok distribution:
|
|
|
|
|
|
% ./configure --prefix=`tde-config --prefix`
|
|
% make
|
|
% make install
|
|
|
|
|
|
Note: --enable-final is not supported.
|
|
|
|
|
|
DEPENDENCIES
|
|
==============
|
|
|
|
Required
|
|
* tdelibs
|
|
http://trinitydesktop.org
|
|
|
|
* TagLib 1.4 (or newer)
|
|
(metadata tagging library)
|
|
http://freshmeat.net/projects/taglib
|
|
|
|
* Ruby 1.8
|
|
(programming language, used for scoring, lyrics, last.fm streams)
|
|
http://www.ruby-lang.org
|
|
|
|
* xine-lib 1.0.2 (or newer)
|
|
Note: xine-lib 1.1.1 is required for gapless playback.
|
|
(multimedia framework)
|
|
https://www.xine-project.org/home
|
|
|
|
Optional
|
|
|
|
* tdebase
|
|
(needed for Konqueror Sidebar)
|
|
http://trinitydesktop.org
|
|
|
|
* MySQL 4 or 5
|
|
(faster database support)
|
|
http://www.mysql.com
|
|
|
|
* PostgreSQL 7.4
|
|
(faster database support)
|
|
http://www.postgresql.org
|
|
|
|
* OpenGL accelerated X-Server
|
|
(visualization rendering)
|
|
|
|
* Libvisual 0.4.0 + SDL 1.2
|
|
(visualization framework)
|
|
http://localhost.nl/~synap/libvisual/
|
|
http://www.libsdl.org
|
|
|
|
* ProjectM 0.96 (or newer)
|
|
(visualization plugins for Libvisual or XMMS)
|
|
http://xmms-projectm.sourceforge.net/
|
|
|
|
* libtunepimp 0.3 (or newer)
|
|
(automatic tagging support)
|
|
http://www.musicbrainz.org/
|
|
|
|
* K3B 0.11 (or newer)
|
|
(CD burning support)
|
|
http://www.k3b.org
|
|
|
|
* libgpod 0.4.2 (or newer)
|
|
(iPod support)
|
|
Note: libgpod 0.6.0 is required for the newest Apple iPods.
|
|
http://www.gtkpod.org/libgpod.html
|
|
|
|
* libifp 1.0.0.2
|
|
(iRiver iFP support)
|
|
http://ifp-driver.sourceforge.net/libifp/
|
|
|
|
* libmp4v2 (mpeg4ip 1.5 is recommended, faad2 is less reliable)
|
|
(MP4/AAC tag reading & writing)
|
|
http://www.sf.net/projects/mpeg4ip
|
|
http://www.audiocoding.com
|
|
|
|
* libnjb 2.2.4 (older versions may work)
|
|
(NJB mediadevice (Creative Nomad/Zen family, Dell DJ devices)
|
|
http://www.sf.net/projects/libnjb
|
|
|
|
* libmtp 0.1.1 (or newer)
|
|
(MTP media device support AKA PlaysForSure)
|
|
http://libmtp.sourceforge.net/
|
|
|
|
* libkarma 0.0.5 && OMFS 0.6.1
|
|
(Rio Karma support via USB)
|
|
http://freakysoft.de/html/libkarma/ && http://linux-karma.sf.net/
|
|
|
|
|
|
|
|
INSTALLATION-FAQ
|
|
==================
|
|
|
|
Q: Can I improve Amarok's startup time?
|
|
A: Prelinking Amarok has spectacular results; however if you have binary openGL
|
|
drivers (eg Nvidia drivers), you will need to compile Amarok --without-opengl
|
|
in order to get the amarokapp binary to prelink (the amarok binary is not
|
|
important here).
|
|
|
|
|
|
INFORMATION FOR PACKAGERS
|
|
===========================
|
|
|
|
For Amarok packages we suggest you build:
|
|
|
|
% ./configure --disable-debug
|
|
|
|
It is possible to build Amarok to use MySQL as the database backend. Using
|
|
MySQL makes the Amarok collection faster.
|
|
|
|
We suggest compiling Os, there is no particular part of Amarok that would
|
|
benefit from optimisation, so the smallest binary is probably the best route.
|
|
|
|
In order to limit the dependencies the Amarok package demands we suggest
|
|
splitting Amarok into the following packages:
|
|
|
|
1. Amarok + one backend
|
|
2. xine-engine
|
|
3. Helix-engine
|
|
4. amarok_libvisual
|
|
5. ipod media device
|
|
6. ifp media device
|
|
7. njb media device
|
|
8. mtp media device
|
|
9. rio karma media device
|
|
|
|
Amarok is modular and will be fully functional as long as one of 2 or 3 is
|
|
also installed. Hence we suggest Amarok + one backend. Feel free to include the
|
|
helix, MAS and NMM engines if you can satisfy their dependencies.
|
|
|
|
Amarok ships with two binaries: amarok and amarokapp. The amarok binary is a
|
|
wrapper designed to speed up command line argument passing. amarokapp is the
|
|
real Amarok.
|
|
|
|
If you make packages for Amarok please let us know and we'll link to you on the
|
|
homepage (as long as you don't object).
|
|
--------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
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, a file
|
|
`config.cache' that saves the results of its tests to speed up
|
|
reconfiguring, and a file `config.log' containing compiler output
|
|
(useful mainly for debugging `configure').
|
|
|
|
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 at some point `config.cache'
|
|
contains results you don't want to keep, you may remove or edit it.
|
|
|
|
The file `configure.in' is used to create `configure' by a program
|
|
called `autoconf'. You only need `configure.in' 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 a while. While running, it prints some
|
|
messages telling which features it is checking for.
|
|
|
|
2. Type `make' to compile the package.
|
|
|
|
3. Type `make install' to install the programs and any data files and
|
|
documentation.
|
|
|
|
4. You can remove the program binaries and object files from the
|
|
source code directory by typing `make clean'.
|
|
|
|
Compilers and Options
|
|
=====================
|
|
|
|
Some systems require unusual options for compilation or linking that
|
|
the `configure' script does not know about. You can give `configure'
|
|
initial values for variables by setting them in the environment. Using
|
|
a Bourne-compatible shell, you can do that on the command line like
|
|
this:
|
|
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
|
|
|
|
Or on systems that have the `env' program, you can do it like this:
|
|
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
|
|
|
|
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 supports 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' will install the package's files in
|
|
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
|
installation prefix other than `/usr/local' by giving `configure' the
|
|
option `--prefix=PATH'.
|
|
|
|
You can specify separate installation prefixes for
|
|
architecture-specific files and architecture-independent files. If you
|
|
give `configure' the option `--exec-prefix=PATH', the package will use
|
|
PATH as the prefix for installing programs and libraries.
|
|
Documentation and other data files will still use the regular prefix.
|
|
|
|
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' can not figure out
|
|
automatically, but needs to determine by the type of host the package
|
|
will run on. Usually `configure' can figure that out, but if it prints
|
|
a message saying it can not guess the host type, give it the
|
|
`--host=TYPE' option. TYPE can either be a short name for the system
|
|
type, such as `sun4', or a canonical name with three fields:
|
|
CPU-COMPANY-SYSTEM
|
|
|
|
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 host type.
|
|
|
|
If you are building compiler tools for cross-compiling, you can also
|
|
use the `--target=TYPE' option to select the type of system they will
|
|
produce code for and the `--build=TYPE' option to select the type of
|
|
system on which you are compiling the package.
|
|
|
|
Sharing Defaults
|
|
================
|
|
|
|
If you want to set default values for `configure' scripts to share,
|
|
you can create a site shell script called `config.site' that gives
|
|
default values for variables like `CC', `cache_file', and `prefix'.
|
|
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
|
`PREFIX/etc/config.site' 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.
|
|
|
|
Operation Controls
|
|
==================
|
|
|
|
`configure' recognizes the following options to control how it
|
|
operates.
|
|
|
|
`--cache-file=FILE'
|
|
Use and save the results of the tests in FILE instead of
|
|
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
|
|
debugging `configure'.
|
|
|
|
`--help'
|
|
Print a summary of the options to `configure', and exit.
|
|
|
|
`--quiet'
|
|
`--silent'
|
|
`-q'
|
|
Do not print messages saying which checks are being made.
|
|
|
|
`--srcdir=DIR'
|
|
Look for the package's source code in directory DIR. Usually
|
|
`configure' can determine that directory automatically.
|
|
|
|
`--version'
|
|
Print the version of Autoconf used to generate the `configure'
|
|
script, and exit.
|
|
|
|
`configure' also accepts some other, not widely useful, options.
|
|
|