bdbca4b3af
Bug fix release Overview of changes in GLib 2.72.1 Fix building projects which use g_warning_once() with clang++ (#2625) Fix g_file_trash() not deleting directories via the portals backend (work by Matthias Clasen) (#2629) A number more compiler warnings fixed for MSVC (work by Loïc Le Page) (!2495) Fix detection of broken poll() function on macOS (work by Haruka Ma) (!2571) Fix spawning subprocesses from GUI programs on Windows (work by Marc-André Lureau) (!2582) Bugs fixed: 2312 gdbus-test-codegen tests leak GWeakRef objects 2625 g_warning_once fails to build with clang++ 2629 g_file_trash() does not work on directories inside a sandbox 2495 Cleanup warnings split 6 2499 Various contenttype-related test fixes on win32 2534 gpowerprofilemonitor: Tweak wording of documentation to make more sense 2540 Various win32 tests skip & fixes 2541 meson: simplify lookup of python command 2543 ci: Update the Fedora CI image to Fedora 34 2556 gdbusconnection: Use g_strv_contains() rather than a home-grown version 2557 gdbusmethodinvocation: Fix a leak on an early return path 2558 Move unit test on g_basename() function to glib/tests/fileutils.c 2559 Move tests/relation-test.c to glib/tests/relation.c 2560 ci: Update Coverity, mingw and Android CI images to Fedora 34 2563 glib: Format GDateTime ISO8601 years as %C%y 2564 Move test files on slices from tests/ to glib/tests/ 2566 tests: Add more tests for GResolver response parsing 2573 Backport translation fixes and !2571 “meson: Set BROKEN_POLL in macOS builds” to glib-2-72 2574 Backport !2565 “Revert "meson: simplify lookup of python command"” to glib-2-72 2587 Backport !2583 “Fix trashing sandboxed directories” to glib-2-72 2588 Backport !2582 “glib/win32: fix spawn from GUI regression” to glib-2-72 2590 Backport !2589 “tests: Don’t exit gdbus-method-invocation test early on connection close” to glib-2-72 2593 Backport !2578 “gatomic: Add a C++ variant of g_atomic_int_compare_and_exchange()” to glib-2-72 Translation updates: Bulgarian Catalan Indonesian Italian Lithuanian Polish Portuguese Russian Slovenian Swedish Turkish Ukrainian (From OE-Core rev: d8222529a1caa2703ed296d8a8274983e738cefc) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit e167060bfb105799e0931c06a6aa1275163bf261) Signed-off-by: Steve Sakoman <steve@sakoman.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.