Skip to content
Warning: the windows branch is treated as a local topic branch that just happens to be shared here, so expect non-fast-forward updates...
C Objective-C Python C++ Perl Shell
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
debian
docs
glib
gmodule
gthread
tests
.cvsignore
AUTHORS
COPYING
ChangeLog
ChangeLog.pre-2-0
ChangeLog.pre-2-10
ChangeLog.pre-2-12
ChangeLog.pre-2-2
ChangeLog.pre-2-4
ChangeLog.pre-2-6
ChangeLog.pre-2-8
HACKING
INSTALL
Makefile.am
NEWS
README
README.win32
acconfig.h
acglib.m4
acinclude.m4
autogen.sh
config.guess
config.h.win32
config.sub
configure.in
garray.c
gbacktrace.c
gcache.c
gcompletion.c
gdataset.c
gdate.c
gerror.c
ghash.c
ghook.c
giochannel.c
giounix.c
giowin32.c
glib-config.in
glib.def
glib.h
glib.m4
glib.spec.in
glibconfig.h.win32.in
glist.c
gmain.c
gmem.c
gmessages.c
gmutex.c
gnode.c
gprimes.c
grel.c
gscanner.c
gslist.c
gstrfuncs.c
gstring.c
gtimer.c
gtree.c
gutils.c
ltconfig
ltmain.sh
makefile.msc
sanity_check
testgdate.c
testgdateparser.c
testglib.c

README

General Information
===================

This is GLib version 1.2.2. GLib is a library which includes support
routines for C such as lists, trees, hashes, memory allocation, and
many other things.

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".
Something went wrong with that request. Please try again.