BBS水木清华站∶精华区

发信人: yuhj (勇  梦回唐朝), 信区: Linux
标  题: Linux下的ICQ - 真正的X界面
发信站: BBS 水木清华站 (Fri Jul 31 10:18:55 1998)

一把非windows平台的ICQ都只能用Java版,优点是兼容性比较好.
缺点就是Java那一套了,速度慢,不稳定等等.这个Licq是某些
好事的hacker通过跟踪反汇编将window版的ICQ移到了Linux下.

跟其他GPL的软件一样,这个东西是用source形式发布.主要的问题是
它是用Qt写的.Qt是一个X下的编程库.RedHat5.1是自己带的,别的东西
我就不知道了.没有Qt的人需要先编译安装qt再编译Licq.
Qt的homepage在http://www.troll.no/

Licq有两个版本现在,0.34是stable版,0.40pre1是development版,
都在ftp.lib.pku.edu.cn/incoming/licq下

我在我的RH5.1上编译它出过一些麻烦,主要是就是连不进一个动态库,
后来是重新编译Qt,编译一个静态库然后连Licq成功的.另外它的
配置也比较麻烦.建议多看看readme

其主页在http://pages.infinit.net/fairoff/licq/

以下是ReadMe

LICQ v0.40pr1 (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.

INSTALLATION:

As root:
1. Autoconf is now supported.  Just 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. Type 'make' and in theory it will build.
3. Type 'make install' and licq will be installed (defaults to
   /usr/local).

As each user:
4. Run licq.inst from /usr/local/bin.
   This will install the licq config and data files from /usr/local/licq
   to ~/.licq.  You can change either of these directories by editing the
   script.
5. You can import users from Micq or ICQJava into Licq using licq.micqconvert
   or licq.javaconvert.  Run these scripts from your personal conf/
   directory.
6. Edit ~/.licq/conf/licq.conf to specify your personal preferences

Licq requires the following:
Qt >= 1.40 (if you are using rpm then it requires the qt and qt-devel rpm)
g++ >= 2.7 (or egcs)
There are many problems with gcc 2.8 and Qt, so watch for that if you have
problems linking.  I use the redhat 5.1 release of Qt from the troll site.  It is
the only one I've found that works with gcc 2.8.  If you use gcc 2.7, then
there might be spurious warnings in places.
Hopefully you can ignore them.

Licq has been compiled and run successfully on the following systems:
Linux/i386
Linux/Alpha
FreeBSD/i386

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.  As far as I know, neither RedHat's nor Troll's are.
The only place I've found an rpm is at ftp.kde.org.  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

--

        信言不美，美言不信。
            善者不辩，辩者不善。
                知者不博，博者不知。
                                <<老子.道德经>>八十一章

※ 来源:·BBS 水木清华站 bbs.net.tsinghua.edu.cn·[FROM: 166.111.120.14]