mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-12-25 23:16:14 +01:00
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
d120d02a8c
Mon Sep 21 23:23:10 CDT 1998 Shawn T. Amundson <amundson@gtk.org> * Released GLib 1.1.3 |
||
---|---|---|
glib | ||
gmodule | ||
tests | ||
.cvsignore | ||
acconfig.h | ||
acinclude.m4 | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
ChangeLog.pre-2-0 | ||
ChangeLog.pre-2-2 | ||
ChangeLog.pre-2-4 | ||
ChangeLog.pre-2-6 | ||
ChangeLog.pre-2-8 | ||
ChangeLog.pre-2-10 | ||
ChangeLog.pre-2-12 | ||
config.guess | ||
config.sub | ||
configure.in | ||
COPYING | ||
garray.c | ||
gbacktrace.c | ||
gcache.c | ||
gcompletion.c | ||
gdataset.c | ||
gerror.c | ||
ghash.c | ||
glib-config.in | ||
glib.h | ||
glib.m4 | ||
glib.spec | ||
glibconfig.h.in | ||
glist.c | ||
gmem.c | ||
gmessages.c | ||
gnode.c | ||
gprimes.c | ||
grel.c | ||
gscanner.c | ||
gslist.c | ||
gstrfuncs.c | ||
gstring.c | ||
gtimer.c | ||
gtree.c | ||
gutils.c | ||
INSTALL | ||
install-sh | ||
ltconfig | ||
ltmain.sh | ||
Makefile.am | ||
missing | ||
mkinstalldirs | ||
NEWS | ||
README | ||
stamp-h.in | ||
testglib.c |
General Information =================== This is GLib version 1.1.3. GLib, is a library which includes support routines for C such as lists, trees, hashes, memory allocation, and many other things. Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior to 1.1.0. The official ftp site is: ftp://ftp.gtk.org/pub/gtk The official web site is: http://www.gtk.org/ A mailing list is located at: gtk-list@redhat.com To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null (Send mail to gtk-list-request@redhat.com with the subject "subscribe") Installation ============ See the file 'INSTALL' How to report bugs ================== To report a bug, send mail either to gtk-list, as mentioned above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you must be subscribed yourself. In the mail include: * The version of GLib * Information about your system. For instance: - What operating system and version - What version of X - For Linux, what version of the C library And anything else you think is relevant. * How to reproduce the bug. If you can reproduce it with the testglib program that is built in the glib/ directory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded. * If the bug was a crash, the exact text that was printed out when the crash occured. * Further information such as stack traces may be useful, but is not necessary. Patches ======= Patches can be uploaded to the incoming/ directory on ftp.gtk.org. Please follow the instructions there, and include your name and email address in the README file. If the patch fixes a bug, it is usually a good idea to include all the information described in "How to Report Bugs".