e54a29b902
0001-Fix-string-literal-concatenation.patch 0001-Fix-literal-as-per-c-11.patch removed since they're included in 2.4 Changelog: ========== * Restore mimetype name for *.bz2 and *.tar.bz2 * Improve detection of application/mac-binhex40 * Add application/x-msdownload and subtypes * Add Windows app store types * Give Windows Installer packages the package icon * Lower priority for text/x-mpsub's magic, so it doesn't match pcb-drillFile.drl * Add application/x-powershell * Add application/wasm * Change comment of text/x-mpsub * Change comment of text/x-mpl2 * Add text/x-component * Give higher priority to the more specific image/apng magic * Recognize *.jfif as image/jpeg * Add application/its+xml * Add text/x-vb * Add text/x-basic * Add new group "chemical" in update-mime-database * Add mimetype for Protein Data Bank (pdb) files * Remove too generic magic from application/x-pak * Add application/json5 * Add text/vbscript.encode * Add text/jscript.encode * Add text/jscript as synonym of text/javascript * Fix backwards relationship between text/javascript and application/ecmascript * Add application/vnd.cups-ppd * Add application/x-ms-shortcut * Give application/x-mswinurl the link icon * Fix missing sentinel warning with clang * Fix false positive fdatasync detection on darwin * Fix string literal concatenation (From OE-Core rev: ec0c733062e8d934c86698bedcd5628a60ef38a5) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> 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.