034223db3b
Changelog: ========== Features added -------------- * The "cythonize" and "cython" commands have a new option "-M" / "--depfile" to generate ".dep" dependency files for the compilation unit. This can be used by external build tools to track these dependencies. The "cythonize" option was already available in Cython :ref:'0.29.27'. Bugs fixed ---------- * "const" fused types could not be used with memory views. Patch by Thomas Vincent. (Github issue :issue:'1772') * "wstr" usage was removed in Python 3.12 and later (PEP-623). (Github issue :issue:'5145') * A type check assertion for Cython functions failed in debug Python builds. (Github issue :issue:'5031') * Fixed various compiler warnings. Patches by Lisandro Dalcin et al. (Github issues :issue:'4948', :issue:'5086') * Fixed error when calculating complex powers of negative numbers. (Github issue :issue:'5014') * Corrected a small mis-formatting of exception messages on Python 2. (Github issue :issue:'5018') * The "PyUnicode_AsUTF8AndSize()" C-API function was missing from the CPython declarations. (Github issue :issue:'5163') * A performance problem in the compiler was resolved when nesting conditional expressions. (Github issue :issue:'5197') * Test suite problems with recent NumPy and CPython versions were resolved. (Github issues :issue:'5183', :issue:'5190') Other changes ------------- * The undocumented, untested and apparently useless syntax "from somemodule cimport class/struct/union somename" was deprecated in anticipation of its removal in Cython 3. The type modifier is not needed here and a plain "cimport" of the name will do. (Github issue :issue:'4905') * Properly disable generation of descriptor docstrings on PyPy since they cause crashes. It was previously disabled, but only accidentally via a typo. Patch by Matti Picus. (Github issue :issue:'5083') * The "cpow" directive of Cython 3.0 is available as a no-op. (Github issue :issue:'5016') (From OE-Core rev: 4c5b05d92d691447d493ce87f32f4af907410c39) Signed-off-by: Wang Mingyu <wangmy@fujitsu.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.