luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-24 14:36:13 +01:00
Code Issues Packages Projects Releases Wiki Activity
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
29,852 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%
5021d002ab
Go to file
Philip Withnall 5021d002ab introspection: Generate separate GIR files for platform specific APIs 
For both GLib and GIO. (GObject, GIRepository and GModule don’t have any
platform specific APIs.)

This is needed for two reasons:
 * If the same GIR file is shipped on multiple platforms, it has no way
   to conditionally define/not-define an API based on the platform (like
   an `#ifdef` in a C header). So we either end up shipping differing
   GIR APIs on different platforms, or shipping a GIR file which
   declares APIs which aren’t resolvable by `dlopen()` on certain
   platforms, and will cause a language runtime error.
 * The API reference documentation is now generated from the GIR, and
   similar problems are present there: if the GIR contains different
   symbols depending on the platform, there is no way to generate API
   documentation for the union of all of them.

The fix is to ensure that there are no conditional symbols in a GIR, by
splitting out the platform specific symbols into platform specific GIR
files. Platform specific documentation can then be generated from these,
in addition to the main, platform agnostic, documentation.

The documentation changes will following in a subsequent commit.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Helps: #3037
2024-02-12 17:54:10 +00:00
.gitlab-ci Revert "ci: Remove not-printable chars from generated junit file" 2024-02-09 20:22:35 +00:00
.reuse reuse: Add dep5 lines for gnulib and libcharset 2024-02-07 12:08:46 +00:00
docs build: Combine duplicate urlmap.js files 2024-02-12 17:54:10 +00:00
fuzzing gthreadedresolver: Move private testing symbols to a private header 2024-02-09 10:05:56 +00:00
gio gio: Remove unnecessary appinfo_sources variable 2024-02-12 17:54:10 +00:00
girepository introspection: Generate separate GIR files for platform specific APIs 2024-02-12 17:54:10 +00:00
glib glib: Install platform specific headers in a separate step 2024-02-12 17:54:10 +00:00
gmodule gio, gmodule, gthread: compile windows resources only in shared build 2024-01-21 18:51:52 +11:00
gobject tests: Rework how slow param test is skipped 2024-02-06 11:01:46 +00:00
gthread gio, gmodule, gthread: compile windows resources only in shared build 2024-01-21 18:51:52 +11: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 Georgian translation 2024-02-12 13:04:38 +00:00
subprojects docs: Add initial support for using gi-docgen for docs 2023-10-11 14:01:28 +01:00
tests tests: Skip lint tests if bash is not available 2024-02-12 14:15:51 +00:00
tools gmessages: introduce g_log_writer_default_set_debug_domains() 2023-11-21 20:49:37 +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 and tar libgirepository documentation 2024-02-12 17:01:15 +00: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: Add a code of conduct document 2022-05-11 12:30:58 +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 Merge branch 'th/meson-werror-fixes-2' into 'main' 2024-02-08 10:28:01 +00:00
NEWS 2.79.1 2024-01-22 14:30:24 +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.