934ad49020
Changelog:
===========
Features added
--------------
* Assigning "const" values to non-const variables now issues a warning.
* Using "noexcept" on a function returning Python objects now issues a warning.
* Some C-API usage was updated for the upcoming CPython 3.13.
* The deprecated "Py_UNICODE" type is no longer used, unless required by user code.
* "std::string.replace()" declarations were added to libcpp.string.
Bugs fixed
----------
* Cython generates incorrect (but harmless) self-casts when directly calling
final methods of subtypes. Lacking a better solution, the errors that recent
gcc versions produce have been silenced for the time being.
* Unused variable warnings about clineno were fixed when C lines in tracebacks are disabled.
* Subclass deallocation of extern classes could crash if the base class uses GC.
* Type checks for Python "memoryview" could use an invalid C function.
* Calling final fused functions could generate invalid C code.
* Declaring extern enums multiple times could generate invalid C code.
* "pyximport" used relative paths incorrectly.
* Running Cython with globbing characters ("[]*?") in the module search path could fail.
* Literal strings that include braces could change the C code indentation.
Other changes
-------------
* The "enum class not importable" warning is now only issued once per enum type.
(From OE-Core rev: 35a7d28d271d2f3e27cf24c2433c4e69c650509e)
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
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.