luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-27 07:56:14 +01:00
Code Issues Packages Projects Releases Wiki Activity
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
27,352 Commits 297 Branches 581 Tags 111 MiB
C 95.3%
Python 2.4%
Meson 1.3%
Objective-C 0.3%
Shell 0.2%
Other 0.5%
d608ceedb3
Go to file
Philip Withnall d608ceedb3 docs: Update security instructions in CONTRIBUTING.md 
Point strongly towards `SECURITY.md` so we are not maintaining security
instructions in multiple places.

Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2023-05-24 16:32:54 +01:00
.gitlab-ci ci: Use Meson 1.0.0 on Windows and macOS CI builds 2023-02-16 13:34:59 +00:00
.reuse docs: Add licensing/copyright data to GVariant specification 2022-11-08 15:46:16 +00:00
docs docs: Move README.win32.md to the docs folder 2023-05-24 16:19:47 +01:00
fuzzing Add fuzzing harness for g_utf8_normalize() 2023-04-14 15:50:47 +00:00
gio Merge branch '3003-glib-compile-schemas-failed' into 'main' 2023-05-23 17:16:27 +00:00
glib tests: Add descriptions to environment tests 2023-05-22 17:33:29 +01:00
gmodule gmodule: Define a gmodule include dependency and use it in gio modules 2023-04-19 21:10:29 +02:00
gobject gobject_gdb.py: small style change to signal name 2023-05-20 02:30:07 +01:00
gthread meson: Add tests for generated pkg-config files 2023-04-17 14:25:52 +02: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 Galician translation 2023-04-27 09:07:30 +00:00
subprojects meson: Don't accidentally pick up intl fallback in the first test 2022-12-31 05:13:10 +05:30
tests Convert tests/assert-msg-test* to glib/tests/assert-msg-test* 2022-06-28 11:19:21 +01:00
tools Merge branch 'valgrind-variable' into 'main' 2023-04-17 12:52:28 +00: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: Disable the Coverity CI job 2023-04-26 14:30:20 +01:00
.gitmodules ci: Update git paths to reflect new GitLab URI 2022-11-02 16:49:51 +00: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: Update security instructions in CONTRIBUTING.md 2023-05-24 16:32:54 +01:00
COPYING docs: Add all used licenses in a REUSE-compatible directory 2022-05-17 17:23:34 +01:00
glib.doap Rename GTK+ to GTK (mostly comments and documentation) 2023-05-10 10:56:44 +07:00
INSTALL.md INSTALL.md,README.win32.md: Actualize links 2023-01-04 11:52:07 +02:00
meson_options.txt build: Add runtime_dir option to set runstatedir path 2022-12-02 21:48:03 +00:00
meson.build gfile: Ensure loff_t is defined on FreeBSD 2023-05-15 16:22:35 +01:00
NEWS 2.76.1 2023-03-22 11:28:01 +00:00
README.md docs: Move README.win32.md to the docs folder 2023-05-24 16:19:47 +01:00
SECURITY.md docs: Update SECURITY to stop mentioning a deprecated mailing list 2022-12-13 19:16:35 +00:00

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.md’. There is separate and more in-depth documentation for building GLib on Windows.

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 GNOME’s 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.