1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
LICQ v0.44 (beta)
An ICQ close written fully in c++ using the Qt widget set. See the webpage
(http://pages.infinit.net/fairoff/licq/index.html) for more information.
Licq implements messages (online and offline), urls, chat, gui configuration,
history as well as a number of other features.
LICENSE
This program is licensed under the terms of the GNU GPL, with the
exception that it may be compiled and linked with the TrollTech QT
library without implying that any of the rights or restrictions
associated with the GPL are applied to the QT library.
INSTALLATION:
(If you have a preconfigured binary distribution then skip to step 3)
As root:
1. Type 'configure' and it will determine all the right settings and
directories for your system. If it fails, try the following manual
directory specifications:
--x-includes=DIR X include files are in DIR
--x-libraries=DIR X library files are in DIR
--with-qt-dir where the root of qt is installed
--with-qt-includes where the qt includes are.
--with-qt-libraries where the qt library is installed.
2. Edit the config.h file to select necessary options. If your system
complains about signedness errors during compilation then uncomment
the #define NEED_SIGNED. If your system does not have inet_aton then
uncomment the #define NEED_INETATON.
3. Type 'make' and in theory it will build.
4. Type 'make install' and licq will be installed (defaults to
/usr/local).
As each user:
5. When you run licq for the first time it will install all the necessary
files in ~/.licq.
6. You can import users from Micq or ICQJava into Licq using licq.micqconvert
or licq.javaconvert. Run these scripts from your personal conf/
directory. You can also import your windows list using licq.winconvert,
which is a perl script and so requires you to have perl installed.
7. Edit ~/.licq/conf/licq.conf to specify your personal preferences for
the graphical interface and sound support. Help is include in said file.
SOCKS5 Proxy Support:
Licq supports SOCKS5 proxies. To enable this support, run configure with
--enable-socks5, and optionally --with-socks5-inc=PATH and
--with-socks5-lib=PATH. Then just make sure all the right environment
variables are set and it should work.
Licq requires the following:
Qt >= 1.40 (if you are using rpm then it requires the qt and qt-devel rpm)
g++ 2.7, 2.8, or egcs.
Licq has been compiled and run successfully on the following systems at one
point (note current versions may no longer compile without a bit of tweaking):
Linux/x86
Linux/Alpha
FreeBSD/i386
AIX/RS6000
NetBSD/mk68000
Sun3/mk68000
Solaris/x86
CONFIGURATION:
Configuration is done through the conf/licq.conf file, which contains .ini
style options. Help on each option is include in the file. The contact
list is stored in conf/users.conf. Each users info is stored as a simple
text file called {user uin}.uin. Again, the options are pretty obvious.
You can add/remove/edit a user inside the gui, or by editing the conf files.
The History file is the file where the user history is stored...you can
specify a filename for each user, or you can put one of the following
keywords:
none : no history file
default : makes the history file history/<uin>.history
USE:
Type licq -h for commandline help.
Using licq is very straight-forward. To access any of the options, just
right click on a user and select the relevant command, or double click on
the user. A window will open containing a tab dialog with all the
possible things to do. In this way you can read a new message, check user
info, and send a message all from the same window at the same time.
One key feature of licq is the network status window, which can be viewed
by selecting "Show Network Window" under the "System" menu. This screen
will show you exactly what is occuring at the protocol level.
The menu option "<your alias>" will allow you to view your own settings
and to check system messages.
You can authorize a user to add you by selecting the menu option "User" -
"Authorize User" and supplying their uin.
PROBLEMS:
See the BUGS file for reports on known bugs and problems.
TROUBLE-SHOOTING:
1. COMPILING
The most common problem with compiling licq is with gcc 2.8 and Qt. It seems
that there are a number of binary incompatibilities between gcc 2.7 and 2.8,
so that trying to link source built with gcc 2.8 to a shared library built
with 2.7 will most often fail.
The warnings I've seen in regards to this are of the type:
1. linking errors about "type_info"
2. linking errors about "QPainter" and "QWidget"
Both of these problems are best solves by upgrading to a version of libqt.so
compiled with gcc 2.8. The only rpm which works with egcs or gcc 2.8 is the
rh51 one from ftp.troll.no. You can also download the src rpm and do a
$ rpm --rebuild <qt version>.src.rpm.
Another possible solution is to add -fno-rtti to the compile line in the Makefile
(ie GCC=g++ -fno-rtti) and/or remove the -O2 optimization. This will mainly work
if your error is of the first type above.
Both of these solutions may result in a successful compile but the program may
segfault at startup.
2. RUNNING
o Segfault at startup. If this occurs, run licq with the -d 1 switch and tell
me how far it gets before segfaulting and I'll try and help.
Good luck.
CONTACTS:
Send any questions, comments, or other complaints to groff@engmail.uwaterloo.ca, uin 2127503
|
