English:Docs:Installation
Kadu
Spis treści |
Introduction
This document is about the installation of Kadu Instant Messenger. This information is based on Mandrake distribution, however installation for other system should be similar.
Packages required
Here is the list of packages required for kadu-0.4.0-RC1mdk.i586.rpm
- Glibc
- Glibc-devel
- glibc_lsb
- freetype2
- libgcc1
- XFree86-libs
- libjpeg62 6b
- liblcms1
- libmng1
- libpng3
- libqt3 version 3.1.0 or higher
- libstdc++5
- zlib1
- libopenssl 0.9.7 (probably even newer)
- libexpat0
- libfontconfig1
- libsndfile version 1.0 or higher
libsndfile is a very important for every Kadu version from 0.4.0 (at least if you want to have some sounds in Kadu -- if not, it is not so important). If your distribution doesn't provide it get it.
Additionally if you want to compile the sources of Kadu, you will need:
- Glibc-devel
- freetype2-devel
- XFree86-devel
- libopenssl 0.9.7-devel (probably even newer)
- zlib1-devel
- libjpeg62-devel 6b
- libpng3-devel
- libqt3-devel version 3.1.0 or higher
- libstdc++5-devel
- libsndfile-devel version 1.0 or higher
The pretty most of listed packages should be already installed in your system. Installation of some packages could depend on installing some other packages first.
The very important thing about compiling the source is having the developers packages (*-devel or *-dev depending on your distribution). They are ABSOLUTELY VITAL. Don't complain about errors during compilation unless you have every devel package corresponding to a package that is required.
Instalation -- Howto
Folow the instructions below:
The installation from the binary package (for beginners)
Note: An installation of Kadu for i586 compatible platform is described here. That means you have one of following processors: Intel Pentium 2 or higher or Celeron procesor, AMD K6 or higher and 32bit Linux. If your platform is somehow different, it's possible that packages for you are build as well, but it won't be concerned it in this section (maybe try the installation from the source?).
The file you need is kadu-version.i586.rpm
Head to http://www.kadu.net/, choose download of package for your distribution (in this case Mandrake). Open your favorite terminal program (for example xterm, Konsole -- known from KDE, or gnome-terminal). Type:
bash-2.05b$ su - Password: (Here you type the password of root -- the administrator of your computer) [root@localhost]#
Go to directory of the downloaded RPM file:
[root@localhost]# cd /the-dir-you-have-rpm-in
Type:
[root@localhost]# rpm -ivh kadu-version.i586.rpm
If everything worked well you got:
[root@localhost]# rpm -ivh kadu-0.3.6-1mdk.i586.rpm Preparing... ########################################### [100%] 1:kadu ########################################### [100%] [root@localhost]#
This means you have Kadu installed in your system. Congratulations! If some problems occured try to satisfy the dependecies (install required packages -- the output of rpm command should tell you much).
[root@localhost]# exit
and then as regular user:
bash-2.05b$ kadu
And from this moment enjoy (probably) the best Gadu-Gadu Instant Messenger. IT IS ADVICED NOT TO RUN kadu FROM root (ADMINISTRATOR) SHELL. IT COULD BREAK THE SAFETY AND RELIABILITY OF YOUR SYSTEM, SO DON'T DO IT!
The installation from the source
The file you need is kadu-version.tar.bz2. You can get it from http://www.kadu.net/ Untar it with the command:
bash-2.05b$ tar xjf kadu-version.tar.bz2
Type:
bash-2.05b$ su Password: (Here you type the password of root -- the administrator of your computer) [root@localhost]# cd kadu
Now you are inside the Kadu installation tree.
There are plenty of modules for Kadu. To choose (at first you can skip this part and continue with the default set) which modules you want the installer to get and install edit the .config (it's hidden) file with your favorite text editor (I hope you know how to use at least one ;)).
The description of .config file should be self-explainary, but in general if you want to add support for some module you got to find its name in file and ensure it's checked as 'y' or 'm'. If it's 'n' just change the letter ;). 'y' means that the module is to be compiled into Kadu without the possibility to disable it. 'm' means that the module is to be compiled separately and to get it work you would have to enable it (in modules manager).
Some modules (like osdhints_notify) depends on other modules (like notify). Then the module that is required MUST be compiled staticaly ('y').
To start compilation type:
[root@localhost]#./configure --prefix=/usr
This will download for you every selected module and try to determine if every needed (by Kadu and the modules you want) library is installed in your system. If it fails, it should generate some output, which tells you what to do. Install the missing libraries (WITH DEVELOPER PACKAGES, for instance libsndfile and libsndfile-devel) and re-run ./configure. If you got no idea what more you need to install the best sollution is to disable the module in .config (set to 'n') and every module that dependends on it.
Note: if you got some problems with libsndfile, ensure that you have installed libsndfile and libsndfile-devel (the link above). Please don't post the problem to forums. You can compile the Kadu without any sound module (just check every sound-related module in .config 'n'), so that it wouldn't need libsndfile anymore.
Every time you change the .config or install missing libraries re-run ./configure.
When ./configure exits successfully you got message like this:
************************************** * Kadu configuration is now complete * **************************************
Kadu 0.4.2 was configured using options specified below:
Installation prefix: [/usr] Use pthread resolving in libgadu: yes Compile with debug symbols: no System signals handling: yes Precompiled headers support: no Link with existing libgadu: no Distribution type information: sources Additional c++ compiler flags:
Static modules: docking notify sound Shared modules: account_management alsa_sound autoaway autoresponder config_wizard dcc dcopexport default_sms dsp_sound encryption ext_info ext_sound hints osdhints_notify screenshot sms spy tcl_scripting voice weather x11_docking Disabled modules: arts_sound desktop_docking echo esd_sound macosx_docking nas_sound speech window_notify wmaker_docking amarok ao_sound filedesc led_notify mail miastoplusa_sms pcspeaker spellchecker tabs xmms xosd_notify
Enabled icon themes: default Disabled icon themes: crystal16 crystal22 nuvola16 nuvola22
Run make now (Linux) or gmake (FreeBSD and others) to compile Kadu.
The message is more than adequate. Type:
[root@localhost]# make
It will produce a lot of output but if the last a few lines doesn't contain the world "error" it is more than possible that it did its work well. [If you like to be sure instead of just make, type make && echo 'Everything clear ;).' (if Everything clear appears on your screen then you can continue).] If so, type:
[root@localhost]# make install
This will install Kadu in prefix directory (set by ./configure's --prefix=/direc/tory option), which means in --prefix=/usr case, that following files will be created:
/usr/bin/kadu -- the Kadu binary /usr/share/kadu/ -- directory that contains themes, etc
probably some other files inside /usr directory.
Some tweaking may be done with ./configure options. Get the list of possible option by running:
./configure --help |less
Setting QTDIR variable -- Howto
Sometimes some problems with QTDIR variable occurs (for instance in Mandrake) so that ./configure can't find Qt library. If you realy have Qt3 library installed and ./configure can't find it you got to find it by yourself. The most possible paths are /usr/lib/qt3, /usr/local/qt3 and /usr/local/lib/qt3. If you know the path type:
[root@localhost]# export QTDIR=/usr/lib/qt3
just before running the ./configure.
!!!EnJoY!!!
text by Quake.
Copyright 2005 GNU Free Documentation License
