c99934f683
Overview of Changes in 4.12.3, 28-09-2023 ========================================= * GtkWindow: - Don't assume titlebars are GtkHeaderBar * GtkTreeView: - Fix a crash in gtk_tree_view_is_blank_at_pos * printing: - Fix some issues with the portal implementation * GSK: - Some optimizations in the GL renderer - Fix memory leaks in the Broadway renderer * demos: - Fix a crash in gtk4-demo * Translation updates Basque Brazilian Portuguese Czech Galician Georgian German Hungarian Kazakh Lithuanian Persian Polish Spanish Swedish Turkish Overview of Changes in 4.12.2, 20-09-2023 ========================================= * GtkTooltip: - Don't cross native boundaries when looking for tooltips * GtkCenterLayout, GtkEntry, GtkSearchEntry: - Fix some issues with baseline handling * GtkSwitch: - Respect text direction * Theme: - Use relative font sizes * GSK: - Make repeated gradients match between GL and cairo - Make rounded rect shrinking match between Vulkan, GL and cairo - Fix parsing of text nodes with color glyphs - Restrict an optimization to the cases where it is correct - Fix rendering of shadows with opacity * macOS: - Clamp damage regions to the surface size * Windows: - Fix missing minimize and maximize buttons * Translation updates Basque Brazilian Portuguese Catalan Chinese (China) Czech Danish Dutch Finnish Galician German Hungarian Italian Kazakh Latvian Lithuanian Slovenian Spanish Turkish (From OE-Core rev: ba738a1e2944468ef3e4d9c9810e98457fcd3b85) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.