122fad505d
Changelog: =========== * test: fix license blurb * linux: fix harmless warn_unused_result warning * darwin: fix build warnings * linux: don't use io_uring on pre-5.10.186 kernels * fs: fix WTF-8 decoding issue * test: enable disabled tcp_connect6_error_fault * test: enable disabled fs_link * test: enable disabled spawn_same_stdout_stderr * linux: handle UNAME26 personality * build: move cmake_minimum_required version to 3.9 * unix: set ipv6 scope id for link-local addresses * unix: match kqueue and epoll code * win,spawn: allow `%PATH%` to be unset * doc: switch to Furo, a more modern Sphinx theme * darwin: make TCP_KEEPINTVL and TCP_KEEPCNT available * win,fs: avoid winapi macro redefinition * linux: add missing riscv syscall numbers * doc: fix broken "Shared library" Wikipedia link * unix: get mainline kernel version in Ubuntu * unix: get mainline kernel version in Debian * build: fix qemu install in CI-unix workflow * unix: disable io_uring close on selected kernels * test: skip tests when ipv6 is not available * ibmi: implement ifaddrs, getifaddrs, freeifaddrs * unix: reset signal counters after fork * win,process: avoid assert after spawning Store app * unix: remove pread/preadv conditionals * unix: remove pwrite/pwritev conditionals * darwin: remove workaround for data corruption bug * src: default to stream=stderr in handle printer * test: switch to new-style ASSERT_EQ macros * zos: correctly get cpu model in uv_cpu_info * test: fix get_passwd2 on IBM i * unix: don't malloc on sync uv_fs_read * freebsd: get fs event path with fcntl * test: switch from ASSERT_* to ASSERT_PTR_* * darwin: workaround apple pthread_cond_wait bug * doc: uv_close should be called after exit callback * test: 192.0.2.0/24 is the actual -TEST-NET-1 * unix: add back preadv/pwritev fallback * unix: rename variable for consistency * unix: merge read/write code into single functions * doc: filename arg to uv_fs_event_cb can be NULL * build,win: we need to link against shell32.lib * unix: no preadv/pwritev workaround if not needed * build: add CI for Windows ARM64 * linux: disable io_uring on 32 bits arm systems * build: run sanitizers on macos ci * misc: export WTF8 conversion utilities * build: fix libuv.a file name for cmake * build: add windows ubsan and clang ci * win: improve accuracy of ProductName between arch (From OE-Core rev: a9a634e37c9af42b54b3bf09cb94553c641d6cf4) 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.