luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-25 23:16: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.
30,271 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%
cd45ba8638
Go to file
Michael Catanzaro cd45ba8638 Correct installation directory of GVariant specification 
548ec9f186 accidentally moved the GVariant
spec to the toplevel /usr/share/doc directory, which is surely not
right. Let's move it back into the glib-2.0 subdirectory.

It's debatable whether this is the best place to install the GVariant
specification, since it's not part of the gi-docgen docs, but surely
it's much better than not putting it in any subdirectory.

Fixes #3351
2024-05-07 14:24:38 -05:00
.gitlab-ci ci: Exclude tests from scan-build analysis runs 2024-04-12 18:44:35 +01:00
.reuse reuse: License all .gitignore files as CC0-1.0 (public domain) 2024-04-17 15:32:42 +01:00
docs Correct installation directory of GVariant specification 2024-05-07 14:24:38 -05:00
fuzzing gthreadedresolver: Move private testing symbols to a private header 2024-02-09 10:05:56 +00:00
gio gapplication: Fix a small leak on an error handling path 2024-05-07 17:04:28 +01:00
girepository girparser: Silence a scan-build NULL pointer dereference warning 2024-04-25 23:57:59 +01:00
glib link with -latomic when needed 2024-05-02 17:54:52 +02:00
gmodule gmodule: Fix various implicit conversions from size_t to smaller types 2024-04-25 12:39:39 +01:00
gobject gclosure: Delete old commented-out non-thread-safe code 2024-04-26 00:21:15 +01:00
gthread docs: spelling and grammar fixes 2024-04-01 11:01:06 +00:00
LICENSES girepository: Add remaining license/copyright SPDX headers 2023-10-25 17:12:25 +01:00
m4macros m4macros: drop unused m4 files 2023-07-30 17:03:07 +04:00
po Update Portuguese translation 2024-05-06 21:24:28 +00:00
subprojects docs: Add initial support for using gi-docgen for docs 2023-10-11 14:01:28 +01:00
tests tests: Update the reuse lint limits 2024-04-17 15:47:02 +01:00
tools girepository: Fix static build under Windows 2024-02-21 12:38:40 +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: Make scan-build errors fatal in CI 2024-04-25 23:58:34 +01:00
.gitmodules ci: Update git paths to reflect new GitLab URI 2022-11-02 16:49:51 +00:00
.lcovrc build: Ignore branches in g_clear_*() functions under lcov 2024-01-18 13:06:10 +00:00
CODE_OF_CONDUCT.md docs: Update Code of Conduct URI 2024-04-12 20:36:29 +01:00
CONTRIBUTING.md ci: Use meson compile rather than bare ninja 2023-08-16 13:07:05 +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 docs: Document issue and merge request triaging and review guidelines 2023-06-29 16:50:00 +01:00
meson_options.txt build: Change default for -Dman-pages from disabled to auto 2023-12-21 16:13:03 +00:00
meson.build link with -latomic when needed 2024-05-02 17:54:52 +02:00
NEWS 2.80.0 2024-03-07 21:35:05 +00:00
README.md Expand security policy to cover previous stable branch 2023-10-03 09:12:37 +01:00
SECURITY.md Expand security policy to cover previous stable branch 2023-10-03 09:12:37 +01: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

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.

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.