Skip to content
GLib
EntityQ1137964· pop 17· linked from 219 articles

thumb|Simplified software architecture of GTK, [[Pango, GDK, ATK, GIO, Cairo and GLib.]] GLib is a bundle of three (formerly five) low-level system libraries written in C and developed mainly by GNOME. GLib's code was separated from GTK, so it can be used by software other than GNOME and has been developed in parallel ever since.

Key facts

Software.name
GLib
Software.author
Shawn Amundson
Software.developer
The GNOME Project et al.
Software.programming language
C
Software.operating system
Linux, Unix-like, macOS, Windows
Software.platform
Cross-platform
Software.genre
Library
Software.license
LGPLv2.1

via Wikipedia infobox

Source code

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system. See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows. Upstream GLib only supports the most recent stable release series, the previous stable release series, and the current development release series. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities. Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing , but this will give you a degraded experience. Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums. Information about your system. For instance: What operating system and version 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 one of the test programs that are built in the tests/ 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. If the bug was a crash, the exact text that was printed out when the crash occurred. Further information such as stack traces may be useful, but is not necessary. Please follow the contribution guide to know how to start contributing to GLib. Patches should be submitted as merge requests to gitlab.gnome.org. Note that you will need to be logged in to the site to use this page. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123): Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.

Excerpt from the source-code README · 3,240 chars · not written by Vinony

Wikidata facts

Show 3 more facts
source code repository URL
gitlab.gnome.org/GNOME/glib.git
software version identifier
2.88.0
Sources (7)

via Wikidata · CC0

~7 min read

Article

8 sections
Contents
  • Features
  • Components
  • Programs for the GLib library
  • History
  • Releases
  • Similar projects
  • References
  • External links

thumb|Simplified software architecture of GTK, [[Pango, GDK, ATK, GIO, Cairo and GLib.]] GLib is a bundle of three (formerly five) low-level system libraries written in C and developed mainly by GNOME. GLib's code was separated from GTK, so it can be used by software other than GNOME and has been developed in parallel ever since.

The name "GLib" originates from the project's start as a GTK C utility library.

Gallery (2)

Connections

Categories