Overview of Changes in 4.10.3, 22-04-2023 ========================================= * Fix a popover positioning regression in 4.10.2 * Fix issues with slow loading files in the file chooser Overview of Changes in 4.10.2, 21-04-2023 ========================================= * Fixed issues: - Holding control to select multiple files broken in filechooser (#5669) - Inspector crash (#5681) - Listbase doesn't account for bottom padding in size_allocate_child (#5380) - Leaking AT contexts (#5690) - OpenGL / Windows: Crash when closing gtk4-widget-factory (#5685) - GTK apps crash on startup when setting cursor-size to 0 on Wayland (#5700) - Segmentation fault: gdk_wayland_toplevel_set_startup_id() needs to null-check display->xdg_activation before using it (#5701) - Possible use-after-free under gtk_scrolled_window_update_use_indicators() (#5684) - Wrong error message in `gtk_init` (#5704) - Segfault when scrolling after changing ListView model (#5763) - Bluetooth panel from the Settings app: clicking in the "Downloads" link no longer opens Nautilus (#5671) - Broadway docs or code is broken (#5662) - Disabled GtkPicture's are not properly themed (#5683) - Setting CSS padding to a GtkTextView gives the context menu an offset (#5695) - A11y: the Showing state is used only for windows (#5194) - Gtk4 expander: CSS nodes mismatch code vs. documentation (#5723) - Invoking gtk inspector on a folder results in a crash (#5729) - Double tap requires very precise touch input (#5580) - Name autocompletion dropdown in the GTK4 FileChooser's Save dialog gets stuck, creates artifacts, jumps around (#5743) - Links are not opened when xdg-desktop-portal OpenURI is not available (#5733) - GtkSnapshot generates no nodes appending whitespace-only layouts (#5747) * Translation updates British English Bulgarian Chinese (China) French Indonesian Korean Russian Serbian Slovenian Turkish Overview of Changes in 4.10.1, 14-03-2023 ========================================= * GtkFileChooser - Improve search performance - Be safe against pathless files - Fix memory leaks - Only show local files in recent files - Show most recent files first - Make files non-selectable in selet_folder mode * GtkListView / GtkColumnView / GtkGridView - Fix scrolling problems - Support CSS border-spacing * GtkComboBox - Fix a size allocation problem * gtk - Size allocation fixes * Accessibility - Miscellaneous property fixes and improvements * Wayland - Fix an ordering problem in surface disposal * Windows - Fix Visual Studio build with older GLib * Translation updates Basque Bulgarian Catalan Czech Danish Finnish Friulian Galician Georgian Hungarian Lithuanian Polish Portuguese Swedish Turkish Ukrainian (From OE-Core rev: 0f07445de85c71926e0901d051d330f29a8486d6) 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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.