Files
meta-openembedded/meta-oe
Wang Mingyu 7ac4668df3 libass: upgrade 0.16.0 -> 0.17.0
Detailed Changes:
==================
- Fix various parts relating to automatic linebreaking
- Fix rendering when hinting was enabled and fontsizes or scales are zero
- Switch build to a non-recursive setup for improved parallelism
- Improve quality of SSA Effects movement
- Further documentation improvements
- Completely invalid Events are now discarded during parsing
- Introduction of LayoutRes{X,Y} script headers
- New AlphaLevel style override to set all alpha values while keeping the color
- Add ASS_FEATURE_WRAP_UNICODE to allow automatic linebreaks in accordance with
  the Unicode line breaking algorithm instead of ASS' much stricter breaking
  rules. For the feature to be available at runtime, libass must be linked
  against the new optional dependency libunibreak.
- Improve VSFilter compatibility:

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-12-05 09:16:24 -08:00
..
2022-08-24 08:26:55 -07:00
2022-12-03 08:11:30 -08:00
2022-12-05 09:16:24 -08:00
2022-12-03 08:11:30 -08:00

meta-oe
=======

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit
e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
packages to fullfit this might have different names on different host distributions
e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu
sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
to share your patches, this is preferred for patch sets consisting of more than one patch.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well,
'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy
to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj <raj.khem@gmail.com>