e9a3625c72
License-Update:
===============
doc/libunistring.texi (Conventions):
Explain the (resultbuf, lengthp) return value convention from the user's point of view.
doc/libunistring.texi (Include files):
Fix documentation of _LIBUNISTRING_VERSION and _libunistring_version (incorrect since 2010-05-14).
Add documentation of _libunistring_unicode_version.
Changelog:
=============
* The data tables and algorithms have been updated to Unicode version 15.1.0.
* New functions u8_pcpy, u16_pcpy, u32_pcpy, similar to mempcpy.
* New functions uc_indic_conjunct_break_name, uc_indic_conjunct_break_byname,
uc_indic_conjunct_break.
* New functions
uc_is_property_prepended_concatenation_mark,
uc_is_property_id_compat_math_start, uc_is_property_id_compat_math_continue,
uc_is_property_ids_unary_operator
and new constants
UC_PROPERTY_PREPENDED_CONCATENATION_MARK,
UC_PROPERTY_ID_COMPAT_MATH_START, UC_PROPERTY_ID_COMPAT_MATH_CONTINUE,
UC_PROPERTY_IDS_UNARY_OPERATOR.
* New constant _libunistring_unicode_version.
* The UTF-8 decoder functions, especially u8_mbtouc, are now more Unicode
Standard compliant.
* The *printf functions no longer support the %n directive, for security
reasons.
* Fixed a bug in the *printf functions: In the %U, %lU, %llU directives, a
negative width given as an argument did not trigger left-justification.
* The functions u16_strstr and u32_strstr now operate in worst-case linear
time.
(From OE-Core rev: f9be1e083df6b2621271a2683eddb84bdf34270a)
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
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.