6af04b3b2a
Changelog: ============= - Speed up handling fonts with very large number of variations: - Drawing by up to 40%. - Calculating glyph extents by up to 15%. - Getting horizontal glyph advances by up to 45%. - Speed up getting horizontal and vertical glyph advances by up to 24%. - Significantly speed up vertical text shaping. - Various documentation improvements. - Various build improvements. - Various subsetting improvements. - Various improvements to Rust font functions (fontations integration) and shaper (HarfRust integration). - Rename harfruzz option and shaper to harfrust following upstream rename. - Implement hb_face_reference_blob() for DirectWrite font functions. - New API: +hb_font_get_glyph_origins_func_t +hb_font_get_glyph_h_origins_func_t +hb_font_get_glyph_v_origins_func_t +hb_font_funcs_set_glyph_h_origins_func() +hb_font_funcs_set_glyph_v_origins_func() +hb_font_get_glyph_h_origins() +hb_font_get_glyph_v_origins() - Fix crasher in the glyph_v_origin function introduced in 11.3.0 - Fix build with non-compliant C++11 compilers that don't recognize the "and" keyword - Fix bug in vertical shaping of fonts without the vmtx table - General shaping and subsetting speedups. - Fix in Graphite shaping backend when glyph advances became negative. - Subsetting improvements, pruning empty mark-attachment lookups. - Don't use the macro name _S, which is reserved by system liberaries. - Build fixes and speedup. - Add a kbts shaping backend that calls into the kb_text_shape single-header shaping library. (From OE-Core rev: 791fd2b2a639af751a8b9a9bce142463a08347aa) Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@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.