root/branches/newapi/licq/INSTALL

Revision 4599, 1.8 kB (checked in by erijo, 2 years ago)

Merged trunk changes r4394:4598 into the newapi branch.

  • Property svn:eol-style set to native
Line 
1Basic Installation of Licq daemon
2=================================
3
4Licq installation consists of two main steps:
5
6    1. Install the Licq daemon
7    2. Install one or more plugins
8
9
10Requirements for the daemon:
11    - A C++ compiler and libstc++-devel
12    - GNU make
13
14    Optional it may be helpful to have these:
15    - OpenSSL (for encrypted connections, please read README.OPENSSL)
16    - SOCKS libraries (for SOCKS5 support)
17
18
19These are the installation instructions:
20
21     If there is no "configure" script or you downloaded sources from
22     CVS then use `make -f Makefile.cvs' to create your configure script.
23     You will need autoconf and automake for this to work:
24     ftp://ftp.gnu.org/gnu/autoconf/
25     ftp://ftp.gnu.org/gnu/automake/
26
27  1. `cd' to the directory where you unpacked Licq sources and type
28     `./configure' to configure the package for your system.
29
30     Running `configure' takes awhile.  While running, it prints some
31     messages telling which features it is checking for.
32
33     If you are curious as to what possible configurable options, see
34     `./configure --help' for a list of all possible options.
35
36  2. Type `make' to compile the package.
37
38  3. Type `make install' to install the programs and any data files and
39     documentation. You have to be 'root' for this to work. Per default
40     files are installed in /usr/local/* if you have not defined a different
41     --prefix=/some/directory.
42 
43  4. `cd plugins' to the plugins directory and install a plugin of your choice.
44     Read the included INSTALL and README files to learn how to do this.
45     You need at least _one_ plugin; without a plugin Licq will not
46     work!
47
48
49USING LICQ
50==========
51
52For information on how to use Licq please have a look into the doc/ directory
53and read the README file and the others. They include very much useful
54information.
Note: See TracBrowser for help on using the browser.