fb6533178a
Changelog: =========== * win: fix leak in uv_os_tmpdir * docs: fix RTD build * win: lazy-load [GS]etThreadDescription symbols * linux: try preadv64/pwritev64 before preadv/pwritev * win: check cwd length before spawning a child process * macos,bsd: handle missing /dev/null in chroot env * doc: fix README link text * win: fix order of FILE_STAT_BASIC_INFORMATION struct fields * macos: increase child process stdio buffer size * doc: add C3 bindings to LINKS.md * unix: remove unnecessary errno.h include in poll.c * win: fix the inconsistency in volume serial number * unix: add thread affinity support on openharmony * unix: enable getrusage for SunOS * unix,win: accept NAN/INFINITY as file timestamps * win: add ENABLE_VIRTUAL_TERMINAL_INPUT raw tty mode * test: handle UV_ENOTSUP in platform_output * doc: fix rendering of threading.html * unix,sunos: enable use of sendmmsg on Solaris and Illumos * unix: handle out of memory in iface name copy * openbsd: do not error out if cpuspeed is not available * test: skip thread_name_threadpool on AIX/IBMi * aix,ibmi: fix undeclared identifiers * unix,sunos: prefer SO_REUSEPORT for load balancing * doc: free lib pointer before function return * test: link with libm * style: rename parameter to match definition * test: support partial output lines in test runner * build: switch from c90 to c11 * linux: allow nul bytes in abstract socket address * sunos: use pipe2 on solaris and illumos * unix: remove TOCTOU issues from uv_pipe_chmod * unix: use pipe_fname if getsockname returns nothing * haiku: use uint32 instead of uint32_t * doc: update thread pool stack size comment * unix: improve uv_loop_init OOM handling * test: merge uv_tcp_connect callbacks * test: skip multievent tests on macOS with TSAN enabled * linux: align CPU quota calculation with Rust * kqueue: improve fs event watcher OOM handling * sunos: improve fs event watcher OOM handling * build: shorten instructions for cmake build (From OE-Core rev: d79b2a4cfcc439d430790500d46ad8966502e7b6) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
|---|---|---|
| bitbake | ||
| contrib | ||
| documentation | ||
| meta | ||
| meta-poky | ||
| meta-selftest | ||
| meta-skeleton | ||
| meta-yocto-bsp | ||
| scripts | ||
| .b4-config | ||
| .gitignore | ||
| .templateconf | ||
| LICENSE | ||
| LICENSE.GPL-2.0-only | ||
| LICENSE.MIT | ||
| MAINTAINERS.md | ||
| MEMORIAM | ||
| oe-init-build-env | ||
| README.hardware.md | ||
| README.md | ||
| README.OE-Core.md | ||
| README.poky.md | ||
| README.qemu.md | ||
| SECURITY.md | ||
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.