Files
meta-openembedded/meta-oe
Andreas Müller efafa9bc1b poppler: upgrade 20.12.1 -> 21.01.0
Release 21.01.0
core:
 * Faster routines for jpeg decoding
 * Fix reading signatures in encrypted files
 * Add white point correction when lcms is used
 * JBIG2Stream: Fix byte counting
 * Fix potential data loss if we try to fetch a non existing Ref after modifying the document
 * Specifically use DeviceGray instead of DefaultGray for softmasks
 * Fix various issues handling broken files
utils:
 * pdftocairo: Setmode binary for windows
 * pdfsig: Add hability to digitally sign files
 * pdftoppm: add options to set DeviceGray/DeviceRGB/DeviceCMYK
 * pdftops: add options to set DeviceGray/DeviceRGB/DeviceCMYK
 * pdfimages: Account for rotation in PPI calculation
qt5:
 * Add hability to digitally sign files
qt6:
 * Add hability to digitally sign files
build system:
 * Enable clang-tidy bugprone-signed-char-misuse

Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2021-01-13 10:22:23 -08:00
..
2020-06-03 15:15:43 -07:00
2020-12-09 10:14:57 -08:00
2021-01-11 15:38:09 -08:00
2020-11-09 13:41:02 -08:00
2020-10-01 10:32:42 -07:00

meta-oe
=======

This layer depends on:

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

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

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>