============= Version 1.5.0 ============= - AdwDialog - Fix widget selection in inspector when presented as a bottom sheet - Fix clicks on the dimming still working with can-closed=true - Demo - Fix <developer> in metainfo - Translation updates - Belarusian - Brazilian Portuguese - Danish - French - Galician - Hungarian - Italian - Kabyle - Kazakh - Latvian - Norwegian Bokmål - Occitan - Slovenian - Swedish - Turkish ============== Version 1.5.rc ============== - Depend on GTK 4.13.4 - Fix layout with GtkSettings:gtk-xft-dpi == 0 - AdwAboutDialog - Support zero-clause bsd license - Fix example - AdwAboutWindow - Support zero-clause bsd license - AdwDialog - Allow bottom sheets to shrink beyond 360px width - Fix a crash when swiping on the dimming - Adjust dimming intensity - AdwNavigationView - Fix signal mentions in push() docs - Disable missing title warning when containing a split view - AdwStatusPage - Fix property notification in set_child() - AdwSwipeTracker - Use a smaller threshold for window handles - AdwToolbarView - Fix a typo in docs - Demo - Fix window.devel demo - Stylesheet - Adjust shade colors in dark - Make .devel not propagate to dialogs - Translation updates - Basque - Belarusian - Catalan - Chinese (China) - Chinese (Taiwan) - Czech - Dutch - Finnish - French - Georgian - Hebrew - Hungarian - Indonesian - Kazakh - Korean - Latvian - Lithuanian - Norwegian Bokmål - Occitan - Persian - Polish - Russian - Spanish - Swedish - Ukrainian ================ Version 1.5.beta ================ - Fix build with libappstream 1.0 - Fix deprecation warning with libappstream 0.16.4 - Fix a build error with MSVC - Add AdwDialog, AdwAlertDialog, AdwPreferencesDialog and AdwAboutDialog - AdwAboutWindow - Don't pre-select the first section on the Legal page - AdwApplicationWindow - Add :dialogs and :visible-dialog - AdwBreakpointBin - Add remove_breakpoint() - Fix focus during transitions - Fix swapping the child during transitions - AdwButtonContent - Horizontally center children - AdwCarousel - Fix carousel scroll behavior with page reordering - AdwComboRow - Don't change selection on filtering - Fix focus when opening the popover - Set the correct state on the selected checkmark - AdwEntryRow - Add :text-length - AdwHeaderBar - Integrate with AdwDialog - Fix visibility after changing :show-back-button - AdwMessageDialog - Add remove_response() - Fix choose() annotations - AdwNavigationView - Fix a warning message - AdwPreferencesWindow - Fix :visible-page and :visible-page-name docs - AdwStyleManager - Support contrast setting in the settings portal - AdwSwipeTracker - Add :allow-window-handle - AdwTabOverview - Allow child focus on out animations - AdwTabView - Keep view alive during ::page-detached - Fix crashes when using :pages - AdwViewSwitcherBar - Fix a warning when empty - AdwWindow - Add :dialogs and :visible-dialog - Demo - Port everything to AdwDialog - Docs - Add a migration guide for adaptive dialogs - Add a favicon - Use the new asides - Fix erroneous <child> use in breakpoints migration guide - Stylesheet - Increase GtkSwitch padding - Align property row title and other row subtitle sizes - Align expander row and combo row arrows - Stop hiding switch shapes - Translation updates - Czech - French - Galician - German - Greek - Hebrew - Hungarian - Norwegian Bokmål - Persian - Russian - Serbian - Slovenian - Turkish - Ukrainian (From OE-Core rev: 95b01b95a99df06e555416ec4834df426bca4c4a) Signed-off-by: Markus Volk <f_l_k@t-online.de> 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.