wangmy
4b0139ba5f
License-Update: the following message removed from LICENSE: android-ifaddrs.h, android-ifaddrs.c, copyright Berkeley Software Design Inc, Kenneth MacKay and Emergya (Cloud4all, FP7/2007-2013, grant agreement n° 289016). Three clause BSD license. Changes since version 1.43.0: ============================= * process: simplify uv__write_int calls * macos: don't use thread-unsafe strtok() * process: fix hang after NOTE_EXIT * darwin: remove EPROTOTYPE error workaround * doc: fix v1.43.0 changelog entries * win: replace CRITICAL_SECTION+Semaphore with SRWLock * darwin: translate EPROTOTYPE to ECONNRESET * android: use libc getifaddrs() * unix: fix STATIC_ASSERT to check what it means to check * unix: ensure struct msghdr is zeroed in recvmmsg * test: test with maximum recvmmsg buffer * unix: don't allow too small thread stack size * bsd: ensure mutex is initialized * doc: add gengjiawen as maintainer * process: monitor for exit with kqueue on BSDs * test: fix flaky uv_fs_lutime test * build: fix cmake install locations * thread,win: fix C90 style nit * build: rename CFLAGS to AM_CFLAGS * doc/guide: update content and sample code * process,bsd: handle kevent NOTE_EXIT failure * test: remove flaky test ipc_closed_handle * darwin: bump minimum supported version to 10.15 * win: return fractional seconds in uv_uptime() * build: export uv_a for cmake * loop: add pending work to loop-alive check * win: use GetTickCount64 for uptime again * win: restrict system DLL load paths * win,errors: remap ERROR_ACCESS_DENIED to UV_EACCES * bench: add 'uv_queue_work' ping-pong measurement * build: fix error C4146 on MSVC * test: fix benchmark-ping-udp * win,fs: consider broken pipe error a normal EOF * document the values of enum uv_stdio_flags * win,loop: add missing uv_update_time * win,fs: avoid closing an invalid handle * fix oopsie from * doc: clarify android api level * win: fix style nits [NFC] * test: fix flaky udp_mmsg test * test: fix ipc_send_recv_pipe flakiness * doc: checkout -> check out * core: change uv_get_password uid/gid to unsigned * hurd: unbreak build on GNU/Hurd * freebsd: use copy_file_range() in uv_fs_sendfile() * test: use closefd in runner-unix.c * Reland "macos: use posix_spawn instead of fork" * android: fix build error when no ifaddrs.h * unix,win: add uv_available_parallelism() * process: remove OpenBSD from kevent list * zos: fix build breakage * process: only use F_DUPFD_CLOEXEC if it is defined * win,poll: add the MSAFD GUID for AF_UNIX * unix: simplify uv__cloexec_fcntl() * doc: add secondary GPG ID for vtjnash * unix: remove uv__cloexec_ioctl() (From OE-Core rev: 87fd543aa802de1c9d4b234096fff8a1cf929f9a) 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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.