Zheng Ruoqin e40eb83ded pugixml: upgrade 1.11.4 -> 1.12
License-Update: year updated to 2022.

Changelog:
=========
Bug fixes:
----------
-Fix a bug in xml_document move construction when the source of the move is empty
-Fix const-correctness issues with iterator objects to support C++20 ranges

XPath improvements:
-------------------
-Improved detection of overly complex queries that may result in stack overflow
 during parsing

Compatibility improvements:
--------------------------
-Fix Cygwin support for DLL builds
-Fix Windows CE support
-Add NuGet builds and project files for VS2022

Build system changes:
--------------------
-All CMake options now have the prefix PUGIXML_. This may require changing
 dependent build configurations.
-Many build settings are now exposed via CMake settings, most notably
 PUGIXML_COMPACT and PUGIXML_WCHAR_MODE can be set without changing pugiconfig.hpp

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-02-23 09:25:19 -08:00
..
2022-02-21 18:12:04 -08:00
2021-08-03 10:21:25 -07:00
2022-02-03 08:44:32 -08:00
2022-02-23 09:25:19 -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>