mirror of https://git.yoctoproject.org/poky synced 2026-04-18 03:32:13 +02:00

Go to file

Markus Volk 2333609ac2 glib-2.0: update 2.82.2 -> 2.82.4

- remove backported patches

Overview of changes in GLib 2.82.4, 2024-12-11
==============================================

* Fix a double-unref crash which affects many apps which use pygobject to
  export objects on D-Bus (#3559, work by Sebastian Dröge, Philip Withnall)

* Bugs fixed:
  - #3559 2.82.3 regression: lollypop crashes on startup (Philip Withnall)
  - !4430 Backport !4427 “Revert "gdbus: Fix leak of method invocation when
    registering an object with closures"” to glib-2-82
  - !4434 Backport !4432 and !4433 “ci: Add release component to automate
    tarball publishing” to glib-2-82

Overview of changes in GLib 2.82.3, 2024-12-09
==============================================

* Fix compatibility with tzdata 2024b (#3502, work by Rebecca N. Palmer and
  Simon McVittie)

* Bugs fixed:
  - #3502 Test regressions with tzdata 2024b (Rebecca N. Palmer)
  - !4357 Backport !4356 “gdatetime test: Do not assume PST8PDT was always
    exactly -8/-7” to glib-2-82
  - !4370 Backport !4350 “glib: Don't require GLIB_DOMAIN to be a NUL-terminated
    string” to glib-2-82
  - !4380 Backport !4378 “gio: Fix GFileEnumerator leaks in gio tools” to
    glib-2-82
  - !4381 Backport !4373 “macos: Remove extraous space from type identifier” to
    glib-2-82
  - !4388 Backport !4232 “refstring: Fix race between releasing and re-acquiring
    an interned GRefString” to glib-2-82
  - !4397 Backport !4395 “appmonitor: Fix warning building test” to glib-2-82
  - !4400 Backport !4398 “grefstring: Mark a variable as potentially unused” to
    glib-2-82
  - !4417 Backport !4415 “gdbus: Fix leak of method invocation when registering
    an object with closures” to glib-2-82

(From OE-Core rev: 63a276d65a2cc34a8cd7756091f7f0b3908cf625)

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2024-12-17 11:41:53 +00:00

bitbake

bitbake: bitbake-config-build: add an alias to bitbake-layers

2024-12-13 11:11:18 +00:00

contrib

contrib/git-hooks: add a sendemail-validate example hook that adds FROM: lines to outgoing patch emails

2020-12-30 14:01:07 +00:00

documentation

system-requirements.rst: add dependencies for pdf builds

2024-12-16 11:04:53 +00:00

README.md

Poky

Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.

Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.

As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.

The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/

OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.

Contribution Guidelines

Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.

Where to Send Patches

As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:

OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):

Git repository: https://git.openembedded.org/openembedded-core/
Mailing list: openembedded-core@lists.openembedded.org

BitBake (files in bitbake/):

Git repository: https://git.openembedded.org/bitbake/
Mailing list: bitbake-devel@lists.openembedded.org

Documentation (files in documentation/):

Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
Mailing list: docs@lists.yoctoproject.org

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
Mailing list: poky@lists.yoctoproject.org

If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.