mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-01-24 04:56:14 +01:00
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
f477518c3a
* README.win32: More text. * config.h.win32 glibconfig.h.win32: Update to match the corresponding generated files on Unix. * makefile.msc: Update with new source files, and gthread library. Use the compiler flag -MD instead of using -D_DLL and "/nodefaultlib:libc msvcrt.lib" in the link phase. * glib.def: Include new functions, drop removed ones. * glib.h: Add comments about main loop and polling on Win32. (In general, it's only for the GIMP's use.) Add Win32 IO Channel functions. Remove the obsoleted old IO Channel stuff (which was in #if 0 already). * giowin32.c: New file. * gmain.c: Include config.h, conditionalize <sys/time.h> inclusion. Add g_poll implementation for Win32 (only for the GIMP's needs for now, it's hard or even impossible to be as clean and generic as on Unix). Implement g_get_current_time on Win32. If threads aren't supported, don't try to wake up main thread's loop. On Win32, use a semaphore and not a pipe to wake up the main loop. * gmessages.c: On Win32, allocate a console window if the standard output handle is invalid before writing to stdout, and reopen stdout to that console window. * giochannel.c: Conditionalize unistd.h inclusion. Some indentation cleanup. * gstrfuncs.c: Include <signal.h>. * gutils.c: On Win32, also check the HOMEDRIVE and HOMEPATH environment variables. * gmodule-dl.c gmodule-dld.c: In _g_module_build_path, don't add the "lib" prefix and ".so" or ".sl" suffix if already there. * gmodule-win32.c: Likewise for the ".dll" suffix. * gthread-posix.c: Conditionalize <sys/time.h> inclusion. |
||
---|---|---|
debian | ||
docs | ||
glib | ||
gmodule | ||
gthread | ||
tests | ||
.cvsignore | ||
acconfig.h | ||
acglib.m4 | ||
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.h.win32 | ||
config.sub | ||
configure.in | ||
COPYING | ||
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 | ||
glibconfig.h.win32 | ||
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 | ||
INSTALL | ||
install-sh | ||
ltconfig | ||
ltmain.sh | ||
Makefile.am | ||
makefile.lcc | ||
makefile.msc | ||
missing | ||
mkinstalldirs | ||
NEWS | ||
README | ||
README.win32 | ||
sanity_check | ||
stamp-h.in | ||
testgdate.c | ||
testgdateparser.c | ||
testglib.c |
General Information =================== This is GLib version 1.1.12. 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".