This repository has been archived by the owner on May 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
267 lines (188 loc) · 9.55 KB
/
README
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
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
,--------------------------------------------------------------------,
| |
| libicq2000 - The C++ ICQ2000/2001 Library |
| |
`--------------------------------------------------------------------'
Version 0.3.2 http://libicq2000.sourceforge.net/
--------------------------------------------------------------------
- Contents -
--------------------------------------------------------------------
1. Features
2. Installation
- 1. Prerequisites
- 2. Compiling
- 3. Installation
3. History
4. Clients
5. More info for developers
- 1. Contributing to libicq2000
- 2. Anonymous CVS
- 3. API
6. Comments, bug fixes, etc..
7. License
--------------------------------------------------------------------
- Features -
--------------------------------------------------------------------
libicq2000 is an opensource C++ library being developed to support the
icq2000/2001 protocol. It is easy for developers to use as the
backbone for their clients' connection to the ICQ network - all the
protocol work is abstracted away in one nice object-orientated
interface.
libicq2000 supports:
- Message sending/receiving
- URL sending/receiving
- SMS sending/receiving, including delivery reports
(SMTP gateway delivery too)
- Status changes
- Authorisation Requests
- "You were added" messages
- Fetching user info from server (both basic and advanced)
- Fetching away messages
- Setting custom away messages
- Direct Connections
- Invisibility, including visible/invisible lists
- Ignore lists
See the TODO for information about planned features in
progress. Please don't duplicate requests for features already
mentioned in the TODO. Send legitimate feature requests to the
libicq2000-devel mailing list on sourceforge:
<[email protected]> (you don't need to
subscribe to post).
libicq2000 is in no way affiliated with 'ICQ' or 'Mirabilis'.
--------------------------------------------------------------------
- Installation -
--------------------------------------------------------------------
------------------------------------------------------------------
- Prerequisites -
------------------------------------------------------------------
You will need:
* libstdc++ library (the standard C++ library)
Distribution Packages required
------------ -----------------
Redhat 7.1 libstdc++-2.96-81.i386.rpm, libstdc++-devel-2.96-81.i386.rpm
Other I'd appreciate any input from people on success/failures.
Redhats
For RPM distributions (Redhat, SuSE, etc..) - make sure you install
the 'development' RPMs for all these libraries as well. Usually these
are called library-devel.rpm or similar. I'm trying to build up a list
of the names of the rpms that are required, so send me info about what
you needed for your distribution if it's not already here.
Debian libstdc++2.10 and libstdc++2.10-dev
(+ Progeny,
etc..)
Sources for these libraries can be found at the following addresses:
libstdc++: http://www.gnu.org/software/gcc/libstdc++/
(should have come with your version of gcc)
------------------------------------------------------------------
- Compiling -
------------------------------------------------------------------
Generic configure instructions can be found in INSTALL. These are the
brief instructions for libicq2000:
1. Type './configure'
2. Type 'make' to compile the package
On some systems that don't have gmake as the default make you might
have to install and explicitly use that (usually named as gmake in
that case).
------------------------------------------------------------------
- Installation -
------------------------------------------------------------------
1. Type 'make install' as root to install the libraries.
Easy as that.
--------------------------------------------------------------------
- History -
--------------------------------------------------------------------
libicq2000 started life out as part of the gtk-- client
ickle. (http://ickle.sourceforge.net).
Since the 0.3.0 release of ickle, libicq2000 has been split off into
it's own release schedule, CVS tree and sourceforge project.
It was always designed to work as a separate library, it seemed now
that there was enough demand for it to warrant splitting development
off.
--------------------------------------------------------------------
- Clients -
--------------------------------------------------------------------
Known clients that use this library are:
* ickle - a gtkmm graphical client
http://ickle.sourceforge.net/
* CenterICQ - a console client
http://konst.org.ua/centericq/
* ICQv7-t - an ICQ transport for Jabber
http://icqv7-t.sourceforge.net/
* IcyJuice - a Mac OS X graphical client
http://www.mitzpettel.com/software/icyjuice.html
* Fire - a Mac OS X graphical client
http://www.epicware.com/fire.html
* Proteus - a Mac OS X graphical client
http://www.indigofield.com/
--------------------------------------------------------------------
- More info for developers -
--------------------------------------------------------------------
------------------------------------------------------------------
- Contributing to libicq2000 -
------------------------------------------------------------------
In the spirit of opensource libicq2000 is a community effort with
contributions welcomely accepted. If it's just a small patch for a bug
fix, or you are wishing to help out more big time in the development
please feel free to contribute.
I'd prefer patches and development related questions to go to the
sourceforge libicq20000-devel mailing list - so they can be seen by
all the developers rather than just me. I'd suggest subscribing,
although you can post even if you aren't subscribed.
For submitting patches, please:
a) Make sure you are working on a recent checked out copy of the
anonymous CVS, often the problem has been fixed already.
b) Follow code conventions in the layout of the code as it is at the
moment.
c) Produce the diff by running 'cvs diff -uN > my-patch.diff'
d) Email the diff to <[email protected]>
I am happy to add developers to the sourceforge project, so they are
able to checkout CVS with write access and contribute directly back
into CVS. This will be a lot easier for both you and me in the long
run, rather than exchanging patches constantly.
------------------------------------------------------------------
- Anonymous CVS -
------------------------------------------------------------------
If you are interested in using libicq2000 with your client, I'd
recommend looking at the latest CVS:
http://sourceforge.net/cvs/?group_id=36654
The modulename is libicq2000. Once you have checked out the sources,
you must run the autogen.sh file to generate configure.
Beware though - the CVS is often unstable inbetween releases. Please
subscribe to the libicq2000-devel mailing list on sourceforge to stay
up to date on what is going on in CVS. You will also probably want to
subscribe to libicq2000-commits, so you can see what work is being
done on the source. If you find a problem in CVS please check back in
the archives for libicq2000-devel to check it hasn't already been
acknowledged/solved.
------------------------------------------------------------------
- API -
------------------------------------------------------------------
You can find doxygen generated documentation on the libicq2000
homepage (the API link on the right).
The API should be more stable now, and I am aiming to avoid breaking
backward compatability in future as much as possible from now onwards.
The examples directory contains the shell example, which shows how to
use the library from the shell simply and how the socket callbacks
interact.
Other good sources of information are the ickle sourcecode, which
should support all the latest features of the API.
--------------------------------------------------------------------
- Comments, bug reports, etc.. -
--------------------------------------------------------------------
Bug reports and development related comments should be sent to:
(You don't need to be subscribed to post to the list)
To keep up to date with the CVS subscribe to:
This will automatically send you a brief summary of commits to CVS
when they are made.
You can send me mail to:
Although the list is the preferred option.
I am available on icq (ICQ# 12137587 Alias bee).
--------------------------------------------------------------------
- License -
--------------------------------------------------------------------
libicq2000 is released under the GNU LGPL license, see COPYING for
copying conditions.