627dc1415c
This reverts commit 252bbcd2078aadc67a49bacd5b2cd4fd348a8dd7. After further discussion in !3511, we’ve decided that there are risks associated with this change, and it’s not the best way of addressing the original problem. The original motivation for the change turned out to be that `-mms-bitfields` was not handled by `windres`, which was receiving it from `pkg-config --cflags glib-2.0` in some projects. However, if `windres` is claiming to accept CFLAGS then it should accept (and ignore) `-mms-bitfields`, since the `-m` family of options are defined in `man gcc`, just like `-I`, `-D`, etc. There is some question that there might still be third party projects which are built with an old enough compiler that `-mms-bitfields` is not the compiler default. For that reason, we should either still continue to specify `-mms-bitfields` in the `.pc` file, or add a test to assert that third party projects are always compiled with `-mms-bitfields` set. But adding a new test for all third-party compilations is risky (if we get it wrong, things will break; and it’s a test which may behave differently on different platforms), so it seems safer to just keep `-mms-bitfields` in `.pc` for now. Once all compilers which we require specify `-mms-bitfields` by default, we can finally drop this flag (without adding a test for third-party compilations). See: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3511
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 you can reproduce it with one of the test programs that are built
in the
- 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.