Low-level core library that forms the basis for projects such as GTK+ and GNOME (minus CoC)
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
@jeffcliff@shitposter.club 26deca0697 typo 2 weeks ago
.gitlab-ci Revert "ci: Remove not-printable chars from generated junit file" 3 weeks ago
.reuse reuse: Add dep5 lines for gnulib and libcharset 3 weeks ago
LICENSES +NIGGER 2 weeks ago
docs new meson policy 3 weeks ago
fuzzing gthreadedresolver: Move private testing symbols to a private header 3 weeks ago
gio Merge branch '3231-gir-symbols-cleanup' into 'main' 3 weeks ago
girepository initialize variable h0 3 weeks ago
glib Submitted By: Bruce Dubbs <bdubbs@linuxfromscratch.org> 3 weeks ago
gmodule gio, gmodule, gthread: compile windows resources only in shared build 1 month ago
gobject tests: Rework how slow param test is skipped 3 weeks ago
gthread gio, gmodule, gthread: compile windows resources only in shared build 1 month ago
m4macros m4macros: drop unused m4 files 7 months ago
po Update Russian translation 3 weeks ago
subprojects docs: Add initial support for using gi-docgen for docs 5 months ago
tests Incorporate some lint checks into `meson test` 3 weeks ago
tools gmessages: introduce g_log_writer_default_set_debug_domains() 3 months ago
.clang-format CI: Code check formating in CI 4 years ago
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 12 years ago
.editorconfig docs: Add .editorconfig file 2 years ago
.gitignore docs: Move INSTALL.in to INSTALL.md 2 years ago
.gitlab-ci.yml CI: Run all style/lint checks before failing 3 weeks ago
.gitmodules ci: Update git paths to reflect new GitLab URI 1 year ago
.lcovrc build: Ignore branches in g_clear_*() functions under lcov 1 month ago
BLFS.instructions typo 2 weeks ago
CODE_OF_CONDUCT.md de-CoC 3 weeks ago
CONTRIBUTING.md not building yet WIP 3 weeks ago
COPYING docs: Add all used licenses in a REUSE-compatible directory 2 years ago
FAQ de-CoC 3 weeks ago
INSTALL.md docs: Document issue and merge request triaging and review guidelines 8 months ago
NEWS de-CoC 3 weeks ago
README.md clarify where upstream comes from 3 weeks ago
SECURITY.md security policy 3 weeks ago
glib.doap Rename GTK+ to GTK (mostly comments and documentation) 10 months ago
meson.build version bump 3 weeks ago
meson_options.txt build: Change default for -Dman-pages from disabled to auto 2 months ago



This is a fork of GLib without a restrictive code of conduct. See FAQ.

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.

The official download location for this project is here.

Upstream project, where all this came from, is https://gitlab.gnome.org/GNOME/glib , but consider using us instead.


See the file INSTALL.md. We do not support NSA/Microsoft Windows.


Caveat Emptor.




API documentation is available online for GLib for the:

All APIs are subject to change post fork.


If you have a question about how to use GLib ask @jeffcliff@shitposter.club

If he can't help, go to gnome.org and figure what they would have done, or pray to Cthulhu and use StackOverflow or something.

Reporting bugs

Create an issue here and let's discuss

In bug reports please include:

  • 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.

Contributing to GLib

Please follow the contribution guide to know how to start contributing to GLib.

Patches should be submitted as merge requests here , not gitlab.gnome.org