| Building amaroK with NMM Support | ||
|---|---|---|
| Prev | ||
Build amaroK with the following commands:
% ./configure --with-nmm
% make
% su -c 'make install' |
The configure script will tell you if you miss Mandatory Dependencies or if it can't find required header files or libraries. If necessary, specify the locations of the needed includes and libraries with --with-extra-includes=/path/to/extra/includes and --with-extra-libs=/path/to/extra/libs, respectively.
You can skip this section if you installed amaroK in the KDE installation directory. Execute kde-config --prefix in a shell to get the prefix for your KDE installation.
If you have chosen to install amaroK to a different directory than the KDE installation directory, e.g. because you're not root, amaroK probably won't be able to find its plugins. This is because amaroK's plugins are registered as KDE services, which are usually installed in the /usr/share/services directory (depending on where KDE has been installed).
That's why you have to add your amaroK installation path to the KDEDIRS variable, which enables KDE to find the amaroK services.
You could export the KDEDIRS environment variable inside a shell, run kbuildsycoca, which rebuilds the system configuration cache, and start amarok afterwards:
% export KDEDIRS=/path/to/amarok/prefix:$KDEDIRS
% kbuildsycoca
% amarok
|
Alternatively you can set the KDEDIRS environment variable before KDE starts.
You can do it for example in your ~/.xsession file. Here is a sample ~/.xsession:
#!/bin/sh
export KDEDIRS=/path/to/amarok/prefix:$KDEDIRS
exec /usr/bin/x-session-manager
|
If you apply the example file you should know what you do, it might happen that you can no longer login!