Files
meta-openembedded/meta-oe
wangmy 07c00ecba6 poppler: upgrade 22.03.0 -> 22.04.0
Changelog:
=========
 core:
  * Fix underline sometimes being drawn only partially
  * Fix Adobe Reader not reading some of the contents we write correctly
  * Fix code that workarounds some broken-ish files
  * FoFiTrueType: Parse CFF2 fonts too
  * FoFiTrueType: Support cmap types 2 and 13
  * Fix a few small memory leaks
  * code improvements

 qt:
  * Handle SaveAs named action
  * Annotations: don't change the text color when changing the font

 utils:
  * pdftotext: print creation and modification date when using htmlmeta param

 glib:
  * Fix returning internal data of temporary strings

 cpp:
  * Fix code incompatibility with MSVC

 build system:
  * poppler internal library is no longer forced to static on MSVC
  * Error out if iconv is not available and the cpp frontend is enabled
  * Require FreeType 2.8

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-04-06 20:25:34 -04:00
..
2022-03-30 07:51:38 -07:00
2022-03-26 18:15:11 -07:00
2022-03-21 08:25:11 -07: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>