| 1 | LICQ v1.3.6 |
|---|
| 2 | |
|---|
| 3 | An ICQ clone written in C and C++ using a plugin system to allow for |
|---|
| 4 | many possible interfaces. |
|---|
| 5 | See the webpage (http://www.licq.org) for more information. |
|---|
| 6 | Licq implements messages (online and offline), urls, chat, full file |
|---|
| 7 | transfer, gui configuration (with the qt-gui or qt4-gui plugin), history as |
|---|
| 8 | well as a number of other features. |
|---|
| 9 | |
|---|
| 10 | |
|---|
| 11 | LICENSE |
|---|
| 12 | |
|---|
| 13 | This program is licensed under the terms of the GNU GPL, a copy |
|---|
| 14 | of which you should have received with this package. |
|---|
| 15 | |
|---|
| 16 | |
|---|
| 17 | INSTALLATION: |
|---|
| 18 | |
|---|
| 19 | (If you have a binary distribution then see the FAQ for how to |
|---|
| 20 | do a manual install. Don't worry it's very easy, any monkey |
|---|
| 21 | could do it.) |
|---|
| 22 | |
|---|
| 23 | 1. Type './configure' and it will determine all the right settings and |
|---|
| 24 | directories for your system. |
|---|
| 25 | 2. Type 'make' and in theory it will build. If you are using a non-GNU system, |
|---|
| 26 | such as FreeBSD or Solaris, you will need the GNU version of make, often |
|---|
| 27 | installed as `gmake'. If you get errors about "void *" see the FAQ. |
|---|
| 28 | 3. Type |
|---|
| 29 | su -c 'make install' |
|---|
| 30 | and licq will be installed (defaults to /usr/local). |
|---|
| 31 | 4. Depending on which GUI you want to use, go to plugins/qt-gui or |
|---|
| 32 | plugins/qt4-gui and follow the directions there (doc/README) to install |
|---|
| 33 | the Qt interface plugin (necessary). |
|---|
| 34 | |
|---|
| 35 | As each user: |
|---|
| 36 | 5. When you run licq for the first time it will install all the necessary |
|---|
| 37 | files in ~/.licq. |
|---|
| 38 | 6. You can import users from a number of other clients into Licq using |
|---|
| 39 | one of the conversion scripts found on the download section of the web |
|---|
| 40 | page or in the licq-data package. |
|---|
| 41 | |
|---|
| 42 | Licq requires the following: |
|---|
| 43 | Some C++ compiler with proper standard c++ headers. |
|---|
| 44 | |
|---|
| 45 | SOCKS5 Proxy Support: |
|---|
| 46 | Licq supports SOCKS5 proxies. To enable this support, run configure with |
|---|
| 47 | --enable-socks5, and optionally --with-socks5-inc=PATH and |
|---|
| 48 | --with-socks5-lib=PATH. Then just make sure all the right environment |
|---|
| 49 | variables are set and it should work. Also read the SOCKS.HOWTO file. |
|---|
| 50 | |
|---|
| 51 | Licq has been compiled and run successfully on the following systems at one |
|---|
| 52 | point (note current versions may no longer compile without a bit of tweaking): |
|---|
| 53 | Linux/amd64 |
|---|
| 54 | Linux/x86 |
|---|
| 55 | Linux/Alpha |
|---|
| 56 | Linux/PPC |
|---|
| 57 | FreeBSD/i386 |
|---|
| 58 | AIX/RS6000 |
|---|
| 59 | NetBSD/mk68000 |
|---|
| 60 | OpenBSD/sparc |
|---|
| 61 | Sun3/mk68000 |
|---|
| 62 | Solaris/x86 |
|---|
| 63 | Unixware |
|---|
| 64 | Solaris/sparc |
|---|
| 65 | |
|---|
| 66 | CONFIGURATION: |
|---|
| 67 | |
|---|
| 68 | Configuration is done through the file ~/.licq/licq.conf, which contains .ini |
|---|
| 69 | style options. The contact list is stored in users.conf. |
|---|
| 70 | Each users info is stored as a simple text file called users/<uin>.Licq. |
|---|
| 71 | Again, the options are pretty obvious. You can add/remove/edit a user inside |
|---|
| 72 | the gui, or by editing the conf files. |
|---|
| 73 | |
|---|
| 74 | The History file is the file where the user history is stored... |
|---|
| 75 | You can specify a filename for each user, or you can put one of the following |
|---|
| 76 | keywords in users/<uin>.Licq: |
|---|
| 77 | history = none :keep no history file for this user |
|---|
| 78 | history = default :makes the history file history/<uin>.Licq.history |
|---|
| 79 | |
|---|
| 80 | |
|---|
| 81 | USE: |
|---|
| 82 | |
|---|
| 83 | Type licq -h for commandline help. |
|---|
| 84 | |
|---|
| 85 | Using licq is fairly straight-forward. Licq itself is merely a daemon |
|---|
| 86 | designed to run various plugin interfaces. I have written an advanted |
|---|
| 87 | gui in qt (qt-gui) which should be used as the default plugin. Once you |
|---|
| 88 | have compiled and installed Licq, unpack the plugins you wish to use into |
|---|
| 89 | the plugins/ directory, compile them, and then install them into |
|---|
| 90 | /usr/local/share/licq/plugins (replace /usr/local with the prefix given |
|---|
| 91 | to configure if necessary). Then start licq with the -p option: |
|---|
| 92 | $ licq -p qt-gui -- ...any options to the plugin... |
|---|
| 93 | |
|---|
| 94 | Note the -- which tells the system to pass any options after that on to the |
|---|
| 95 | first plugin in the list. Multiple plugins can be chained in this way: |
|---|
| 96 | $ licq -p qt-gui -p email-forward -- <qt-gui options> -- <email-forward options> |
|---|
| 97 | |
|---|
| 98 | |
|---|
| 99 | PROBLEMS: |
|---|
| 100 | |
|---|
| 101 | See the BUGS file for reports on known bugs and problems. |
|---|
| 102 | |
|---|
| 103 | |
|---|
| 104 | TROUBLE-SHOOTING: |
|---|
| 105 | |
|---|
| 106 | 1. RUNNING |
|---|
| 107 | o Segfault at startup. If this occurs, run licq with the -d 15 switch and tell |
|---|
| 108 | me how far it gets before segfaulting and I'll try and help. You can report |
|---|
| 109 | such problems to the mailinglist licq-devel@lists.sourceforge.net. |
|---|
| 110 | |
|---|
| 111 | Good luck. |
|---|
| 112 | |
|---|
| 113 | |
|---|
| 114 | CONTACTS: |
|---|
| 115 | |
|---|
| 116 | Send any questions, comments, or other complaints to |
|---|
| 117 | licq-devel@lists.sourceforge.net. |
|---|
