Low-level core library that forms the basis for projects such as GTK+ and GNOME.
Go to file
Philip Withnall 7b52ccbfc4 Revert "gio, glib: Use G_OS_DARWIN for code that is for such environments"
This reverts commit 476e33c3f3.

We’ve decided to remove `G_OS_DARWIN` in favour of recommending people
use `__APPLE__` instead. As per the discussion on #2802 and linked
issues,
 * Adding a new define shifts the complexity from “which of these
   platform-provided defines do I use” to “which platform-provided
   defines does G_OS_DARWIN use”
 * There should ideally be no cases where a user of GLib has to use
   their own platform-specific code, since GLib should be providing
   appropriate abstractions
 * Providing a single `G_OS_DARWIN` to cover all Apple products (macOS
   and iOS) hides the complexity of what the user is actually testing:
   are they testing for the Mach kernel, the Carbon and/or Cocoa user
   space toolkits, macOS vs iOS vs tvOS, etc

Helps: #2802
2022-11-07 11:30:32 +00:00
.gitlab-ci Merge branch 'wip/3v1n0/support-can-fail-tests' into 'main' 2022-10-31 14:28:02 +00:00
.reuse docs: Mark .wrap files as uncopyrightable 2022-07-05 12:15:15 +01:00
docs Merge branch 'variant-docs' into 'main' 2022-11-02 09:40:24 +00:00
fuzzing fuzzing: Add a new fuzz test for g_variant_byteswap() 2022-10-27 12:13:13 +01:00
gio Revert "gio, glib: Use G_OS_DARWIN for code that is for such environments" 2022-11-07 11:30:32 +00:00
glib Revert "gio, glib: Use G_OS_DARWIN for code that is for such environments" 2022-11-07 11:30:32 +00:00
gmodule Revert "gio, glib: Use G_OS_DARWIN for code that is for such environments" 2022-11-07 11:30:32 +00:00
gobject Revert "gio, glib: Use G_OS_DARWIN for code that is for such environments" 2022-11-07 11:30:32 +00:00
gthread Fix symbol visibility macros on Windows 2022-10-13 20:53:56 -04:00
LICENSES Add a SPDX LicenseRef for the license historically used for tests 2022-11-02 12:34:19 +00:00
m4macros m4macros: Increment serial number of glib-2.0.m4 2021-01-27 11:55:37 +00:00
po Update Dutch translation 2022-11-02 19:09:08 +00:00
subprojects replace pcre1 with pcre2 2022-07-12 11:46:34 +00:00
tests Convert tests/assert-msg-test* to glib/tests/assert-msg-test* 2022-06-28 11:19:21 +01:00
tools tools: Reformat gen-visibility-macros.py with black 2022-10-14 18:15:25 +01:00
.clang-format CI: Code check formating in CI 2019-11-21 14:03:01 -06:00
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 2012-07-30 04:09:08 -04:00
.editorconfig docs: Add .editorconfig file 2021-10-28 14:47:53 +01:00
.gitignore docs: Move INSTALL.in to INSTALL.md 2022-05-11 13:02:49 +01:00
.gitlab-ci.yml ci: Build with -Wnonnull 2022-11-04 14:06:48 -04:00
.gitmodules build: Move gvdb to a subproject 2022-06-16 10:12:07 +01:00
.lcovrc build: Move lcovrc file to root so it’s picked up by Meson 2022-04-28 11:57:45 +01:00
CODE_OF_CONDUCT.md docs: Add a code of conduct document 2022-05-11 12:30:58 +01:00
CONTRIBUTING.md docs: Add a testing policy 2022-06-14 15:19:32 +01:00
COPYING docs: Add all used licenses in a REUSE-compatible directory 2022-05-17 17:23:34 +01:00
glib.doap docs: Sync glib.doap to set of users listed in CODEOWNERS 2022-06-22 15:54:49 +01:00
HACKING docs: Move README.rationale to docs subdirectory 2022-05-11 13:02:49 +01:00
INSTALL.md docs: Reformat INSTALL.md as Markdown 2022-05-11 13:02:55 +01:00
meson_options.txt gio: Optionally install trigger executables to architecture-specific paths 2022-07-24 11:19:37 +01:00
meson.build build: Check for invalid parameter overriding on Windows 2022-11-03 00:11:45 +08:00
msvc_recommended_pragmas.h msvc_recommended_pragmas.h: Refine for clang-cl 2021-03-30 16:45:07 +08:00
NEWS 2.74.0 2022-09-17 20:38:17 +02:00
README.md docs: Move INSTALL.in to INSTALL.md 2022-05-11 13:02:49 +01:00
README.win32.md README.win32.md: Mention about Window 8+ SDK requirement 2021-02-28 11:04:29 +02:00
SECURITY.md docs: Add a note about git-evtag to SECURITY.md 2021-09-07 11:21:12 +00:00

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.md'

Supported versions

Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.

See SECURITY.md for more details.

Documentation

API documentation is available online for GLib for the:

Discussion

If you have a question about how to use GLib, seek help on GNOMEs Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib.

Reporting bugs

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 incoming+gnome-glib-658-issue-@gitlab.gnome.org, 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.

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