Files
meta-openembedded/meta-oe
Wang Mingyu 94d2364152 xmlsec1: upgrade 1.3.2 -> 1.3.3
0001-nss-nspr-fix-for-multilib.patch
change-finding-path-of-nss.patch
ensure-search-path-non-host.patch
fix-ltmain.sh.patch
refreshed for 1.3.3

Changelog
========
-Disabled KeyValue and DEREncodedKeyValue XML nodes by default. Use the
 '--enabled-key-data' option for the xmlsec command line utility or update
 the 'keyInfoCtx->enabledKeyData' parameter if you need to re-enable these
 nodes (also see question 3.5 in the FAQ).
-Removed '--enable-size-t' ('size_t' for MSVC builds) option and made
 'xmlSecSize' to always be the same as 'size_t'.
-Removed previously deprecated functions, defines, etc.
-Fixed build for libxml2 v2.12.0.
-Removed support for OpenSSL 1.1.0 (end of life in Aug 2016).
 The minimum OpenSSL supported version is 1.1.1; the version 3.0.0 or greater is recommended.
-Added runtime check for the enabled algorithms in NSS.
-Removed NT4 support.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2024-01-08 19:54:43 -08:00
..
2023-12-18 22:17:24 -08:00
2023-11-10 09:13:39 -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 ' 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