9e7de16884
Bring in these changes * 6009708b4367 Revert "[runtimes] Add missing test dependencies to check-all (#72955)" * 04caadc61fa2 [Driver] Enable __float128 support on X86 on FreeBSD / NetBSD (#72788) * e919a83f96fe eliminate python SyntaxWarnings from check-all output. * f6c231c15ec8 [clang-format] Fix crashes in AlignArrayOfStructures (#72520) * f74f3e6f58d3 [clang] Fix sorting module headers (#73146) * 7e30ce9528d9 [JITLink][aarch32] Change writeRegister's return type to void. * 03373fd9cb6c [CMake] Support building shared library for NetBSD * 21af3b62b632 workflows/release-binaries: Do a preliminary build to fill ccache (#72576) * 201faeca595e Add RV64 constraint to SRLIW (#69416) * e957e6dcb29d [runtimes] Add missing test dependencies to check-all (#72955) * f8575ff46f89 [clang-format] Fix a bug in aligning comments above PPDirective (#72791) * a71237b9f67f [clangd] Avoid null result in FindRecordTypeAt() * 308c816de5a4 Bump version to 17.0.6 * 442401f7c0ca remove tests from bad merge * 76c7e0e1e2d1 Use the correct namespace for looking up matching operator!= (#68922) * b5cbb35408a3 [libc++] Use correct size for deallocation of arrays in shared_ptr (#68233) * e6de86cb9ef8 Revert "Reland [clang] Canonicalize system headers in dependency file when -canonical-prefixes" (#71697) * bb66d8f8f73b [clang][WebAssembly] Link crt1 even in case of -shared (From OE-Core rev: eab3ce3184d66a98fe9f5992c462552dfc89397f) Signed-off-by: Khem Raj <raj.khem@gmail.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.