e034d3ff56
============= Version 1.5.1 ============= - AdwAboutDialog/Window - Fix an outdated appstream reference in docs - AdwActionRow - Mention .property in docs - AdwAlertDialog - Fix the accessible role - Fix initial focus - AdwAvatar - Fix portrait avatars on hidpi - AdwBin - Fix a potential focus issue - AdwBreakpoint - Fix add_setter() annotations - AdwCarousel - Fix a build warning - AdwComboRow - Fix initial checkmark - Handle model changes properly - AdwDialog - Fix accessibility warnings - Make shortcuts work when there are no focusable widgets - Correctly restore focus when opening a dialog from a menu - Fix GtkWindow:deletable=false hiding close buttons in dialogs - AdwExpanderRow - Fix get_title_lines() and get_subtitle_lines() return types - Fix remove() docs - AdwOverlaySplitView - Unmap sidebar when it's hidden - AdwPreferencesGroup - Fix a potential focus issue - Fix :header-group annotations and notifications - AdwPreferencesPage - Fix a potential focus issue - AdwTabView - Document :close-page return value - Fix a leak when closing the last page - AdwViewStack - Fix a typo in docs - Docs - Update screenshots - Stylesheet - Fix entry progress bars - Add missing return annotations - Translation updates - Brazilian Portuguese - Hindi - Kabyle - Portuguese - Slovak (From OE-Core rev: 301470de9a1a6a44de9a3d7c815e86dba162da68) 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.