forked from AuroraMiddleware/gtk
7b9b0ab0fa
Mon Aug 17 01:40:00 1998 Tim Janik <timj@gtk.org>
* configure.in: version bump to 1.1.1, binary age 0, interface age 0.
pass "gmodule" to AM_PATH_GLIB, with that we require libgmodule.so now.
* gtk/gtkmain.c (gtk_init): since glib's g_return*_if_fail macros log
with G_LOG_LEVEL_CRITICAL now, i added "--g-fatal-checks",
"--gdk-fatal-checks" and "--gtk-fatal-checks". that makes up six
different *-fatal-* arguments now. this needs to be revised and
compressed to a reasonable amount of arguments.
76 lines
2.3 KiB
Plaintext
76 lines
2.3 KiB
Plaintext
General Information
|
|
===================
|
|
|
|
This is GTK+ version 1.1.2. GTK+, which stands for the Gimp ToolKit,
|
|
is a library for creating graphical user interfaces for the X Window
|
|
System. It is designed to be small, efficient, and flexible. GTK+ is
|
|
written in C with a very object-oriented approach.
|
|
|
|
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 GTK
|
|
|
|
* 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 testgtk program that is built
|
|
in the gtk/ subdirectory, 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.
|
|
|
|
(Bugs that can be reproduced within the GIMP are almost as good
|
|
as bugs that can be reproduced in testgtk. If you are reporting a
|
|
bug found with the GIMP, please include the version number of the GIMP
|
|
you are using)
|
|
|
|
* 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. If you do send a stack trace, and the error
|
|
is an X error, it will be more useful if the stacktrace
|
|
is produced running the test program with the --sync command
|
|
line option.
|
|
|
|
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".
|