tree: 1ed23b28f45a28cd112bffd1a81b713c369b927e [path history] [tgz]
  1. .clang-format
  2. .dir-locals.el
  3. .gitattributes
  4. .gitignore
  5. .gitlab-ci.yml
  6. .gitlab-ci/
  7. AUTHORS
  8. CONTRIBUTING.md
  9. COPYING
  10. HACKING
  11. INSTALL.in
  12. NEWS
  13. NEWS.pre-1-3
  14. README
  15. README.md
  16. README.rationale
  17. README.win32
  18. README.win32.md
  19. SECURITY.md
  20. check-abis.sh
  21. clang-format-diff.py
  22. docs/
  23. fuzzing/
  24. gio/
  25. glib-gettextize.in
  26. glib.doap
  27. glib.supp
  28. glib/
  29. gmodule/
  30. gobject/
  31. gthread/
  32. m4macros/
  33. meson.build
  34. meson_options.txt
  35. msvc_recommended_pragmas.h
  36. po/
  37. subprojects/
  38. template-tap.test.in
  39. template.test.in
  40. tests/
README.md

GLib

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 locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file ‘INSTALL.in

How to report bugs

Bugs should be reported to the GNOME issue tracking system. (https://gitlab.gnome.org/GNOME/glib/issues/new). You will need to create an account for yourself.

In the bug report 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.

Patches

Patches should also be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123): Closes: #123

Otherwise, create a new merge request that introduces the change, filing a separate issue is not required.

Default branch renamed to main

The default development branch of GLib has been renamed to main. To update your local checkout, use:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main