Tim Orling
5b26a2b507
* Add comment about riscv32gc ioctl codes patch, it is needed until libc version is 0.2.172 or greater in Cargo.lock. Comparing changes since 1.8.3: https://github.com/PyO3/maturin/compare/v1.8.3...v1.8.6 Changelog: 1.8.6 * Print a message when overriding platform tag from _PYTHON_HOST_PLATFORM in #2594 * Use the current python interpreter's version when the abi3 feature is set with no explicit version in #2597 1.8.5 * Fix release CI build 1.8.4 * Install a Rust toolchain into a temporary directory when building maturin itself or a package and a Rust toolchain is missing. Set MATURIN_NO_INSTALL_RUST to disable this behavior. #2421 * Fix broken maturin develop with latest uv in #2584 * Add PYO3_PYTHON env var support in #2534 * Sort RECORD file in wheel archives to make them deterministic in #2550 * Publish wheel for loongarch64 in #2548 * Add --compression-level option to build command in #2572 (From OE-Core rev: 92387900825dc6570c9bb43ca4b5a7d44f821f5c) Signed-off-by: Tim Orling <tim.orling@konsulko.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.