b2ba5f738a
Bug fix release: appsrc: Clarify buffer ref semantics in signals documentation appsrc: fix annotations for bindings typefind: Skip extension parsing for data:// URIs, fixing regression with mp4 files serialised to data uris playbin3: various fixes playbin3: fix missing lock when unknown stream type in pad-removed cb decodebin3: fix collection leaks decodebin3: Don't duplicate stream selections discoverer: chain up to parent finalize methods in all our types to fix memory leaks glmixerbin: slightly better pad/element creation gltransformation: let graphene alloc its structures memory aligned ogg: fix possible buffer overrun rtpbasepayload: Don't write header extensions if there's no corresponding... rtpbasepayload: always store input buffer meta before negotiation rtpbasepayload: fix transfer annotation for push and push_list subparse: don't try to index string with -1 riff-media: fix memory leak after usage for g_strjoin() playbin/playbin3: Allow setting a NULL URI playsink: Complete reconfiguration on pad release. parsebin: Expose streams of unknown type pbutils: Fix wmv screen description detection subparse: don't deref a potentially NULL variable rawvideoparse: set format from caps in gst_raw_video_parse_set_config_from_caps videodecoder: release stream lock after handling gap events videorate: fix assertion when pushing last and only buffer without duration videorate: Revert "don't reset on segment update" to fix segment handling regressions gst-play-1.0, gst-launch-1.0: Enable win32 high-resolution timer also for MinGW build (From OE-Core rev: 19e9c0b2ac92f9ffc3bcea8ce4761c81326ea4a7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 905766e63a6159535b9da86c4f0af62956285199) 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.