mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-08-24 09:58:54 +02:00
1b9116f9e4
* Makefile.am: Don't distribute glibconfig.h.win32.in, but glibconfig.h.win32. Generate it when making a dist. Also generate makefile.msc and config.h.win32 from corresponding .in files when making dist. * configure.in: Also substitute @GLIB_INTERFACE_AGE@ and @GLIB_BINARY_AGE@ (needed in config.h.win32). * glibconfig.h.win32.in: Use static mutex structure and initial value corresponding to the 1999-04-07 snapshot of pthreads-win32. * tests/Makefile.am: Distribute makefile.msc. Generate it when making dist. * tests/makefile.msc.in: New file. * tests/node-test.c: Include <stdlib.h> for exit().
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".