Google Git
Sign in
fuchsia / third_party / github.com / GNOME / glib / refs/heads/upstream/cherry-pick-255fa26b
commit081d9923e122f50b1f280339dad3170fcad61a30[log] [tgz]
authorGeorges Basile Stavracas Neto <georges.stavracas@gmail.com>Thu Sep 29 17:18:10 2022 -0300
committerGeorges Basile Stavracas Neto <georges.stavracas@gmail.com>Fri Sep 30 13:06:18 2022 +0000
tree1598768048cbfcbef435d3c3a821cdb15928be34
parent45b8685458a95a8a80eeab7758854b7ee5e236f9 [diff]
build: Let Meson figure out Python installation

Commit 4a4d9eb6624 initially switched Meson to find the python
program using find_program('python3'). Sadly that caused a
regression, since in some cases with MSVC it would fallback to
'meson.exe runpython', which is undesired.

However, that particular code was reverted back to an also
undesired lookup method, find_installation('python3'). This
way of finding python also breaks on Windows + MSVC, in particular
when setting it up as follows:

```
winget install python
winget install meson
```

This fails building GLib with:

> python3 not found

Fix that by not passing any argument to find_installation(), which
lets Meson figure it all out by itself.


(cherry picked from commit 255fa26b964bbcd22150dafbfe5ead0acf0b84ad)
1 file changed
tree: 1598768048cbfcbef435d3c3a821cdb15928be34
  1. .gitlab-ci/
  2. docs/
  3. fuzzing/
  4. gio/
  5. glib/
  6. gmodule/
  7. gobject/
  8. gthread/
  9. m4macros/
  10. po/
  11. subprojects/
  12. tests/
  13. .clang-format
  14. .dir-locals.el
  15. .editorconfig
  16. .gitattributes
  17. .gitignore
  18. .gitlab-ci.yml
  19. AUTHORS
  20. check-abis.sh
  21. clang-format-diff.py
  22. CONTRIBUTING.md
  23. COPYING
  24. glib-gettextize.in
  25. glib.doap
  26. glib.supp
  27. HACKING
  28. INSTALL.in
  29. meson.build
  30. meson_options.txt
  31. msvc_recommended_pragmas.h
  32. NEWS
  33. NEWS.pre-1-3
  34. README
  35. README.md
  36. README.rationale
  37. README.win32
  38. README.win32.md
  39. SECURITY.md
  40. template-tap.test.in
  41. template.test.in
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.in’

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.

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