ac40ccb378
Changes from version 1.20.2 aacparse: Avoid mismatch between src_caps and output_header_type avidemux: Fix integer overflow resulting in heap corruption in DIB buffer inversion code (Security fix) deinterlace: Clean up error handling code flvdemux: Actually make use of the debug category gtkglsink: Fix double-free when OpenGL can't be initialised jack: Add support for detecting libjack on Windows matroskademux: Avoid integer-overflow resulting in heap corruption in WavPack header handling code (Security fix) matroskademux, qtdemux: Fix integer overflows in zlib/bz2/etc decompression code (Security fix) qtdemux: Don't use tfdt for parsing subsequent trun boxes rtpbin: Avoid holding GST_RTP_BIN_LOCK when emitting pad-added signal (to avoid deadlocks) rtpptdemux: Don't GST_FLOW_ERROR when ignoring invalid packets smpte: Fix integer overflow with possible heap corruption in GstMask creation. (Security fix) smpte: integer overflow with possible heap corruption in GstMask creation (Security fix) soup: fix soup debug category initialisation soup: Fix plugin/element init v4l2: Reset transfer in gst_v4l2_object_acquire_format() vpxenc: fix crash if encoder produces unmatching timestamp wavparse: ensure that any pending segment is sent before an EOS event is sent (From OE-Core rev: 4aee173335f8d0d0723d629a0dd16a0d1c4ce463) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 66ba273c10b7d738f18620b5a2883d735fff3162) 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.