1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 05:29:32 +00:00
Wang Mingyu 2f38922d03 harfbuzz: upgrade 9.0.0 -> 10.0.1
Changelog:
============
- Relax sanitization checks for "morx"subtables to fix broken AAT shaping of
macOS 15.0 version of GeezaPro.
- Unicode 16.0.0 support.
- Various documentation fixes.
- Various build fixes.
- Add API to allow HarfBuzz client to set what glyph to use when a Unicode
  Variation Selector is not supported by the font, which would allow the client
  to customize what happens in this case, by using a different font for example.
- Add a callback to for "hb_face_t"for getting the list of table tags. This is
  now used to make calling "hb_face_get_table_tags()"work on a faces created by
  "hb_face_create_for_tables()"(e.g. faces returned by "hb_subset_or_fail()").
- CGJ and Mongolian Variation Selectors are now ignored during glyph
  positioning, previously they would block both glyph substitution and
  positioning across them.
- Support cairo script as an output format for "hb-view"command line tool.
- Drop an optimization that would cause HarfBuzz not apply pair positioning
  lookup subtables under certain circumstances, for compatibility with other
  implementations that do apply these subtables.
- Subsetting will now fail if source font has no glyphs, so feeding the subsetter
  invalid data will not silently return an empty face.
- If after partially instancing a font no variation data is left (the instance
  is fully static), don't consider this a failure.
- Workaround a Firefox bug in displaying SVGs generated be "hb-view"command
  line tool under certain circumstances.
- Fix bug in macroman mapping for "cmap"table.
- Fix difference shaping output when HarfBuzz is built with with
  "HB_NO_OT_RULESETS_FAST_PATH"enabled.
- Various subsetting and instancing fixes.
- Various fuzzing fixes.
- Add "with_libstdcxx"meson build option.
- New API:
  HB_SCRIPT_GARAY
  HB_SCRIPT_GURUNG_KHEMA
  HB_SCRIPT_KIRAT_RAI
  HB_SCRIPT_OL_ONAL
  HB_SCRIPT_SUNUWAR
  HB_SCRIPT_TODHRI
  HB_SCRIPT_TULU_TIGALARI
  hb_buffer_set_not_found_variation_selector_glyph()
  hb_buffer_get_not_found_variation_selector_glyph()
  hb_get_table_tags_func_t
  hb_face_set_get_table_tags_func()

(From OE-Core rev: 832272063fe58577b9d959d7dbd4f92d9c22670e)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-10-11 12:17:02 +01:00
2024-10-11 12:17:02 +01:00
2024-02-19 11:34:33 +00:00
2021-07-19 18:07:21 +01:00
2023-10-19 11:31:13 +01:00

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

S
Description
No description provided
Readme 261 MiB