Files
meta-openembedded/meta-oe
Markus Volk c1b13a0682 pugixml: upgrade 1.12 -> 1.13
v1.13 2022-11-01
Maintenance release. Changes:

Improvements:
- xml_attribute::set_value, xml_node::set_value and xml_text::set now have overloads that accept pointer to non-null-terminated string and size
- Improve performance of tree traversal when using compact mode (PUGIXML_COMPACT)

Bug fixes:
- Fix error handling in xml_document::save_file that could result in the function succeeding while running out of disk space
- Fix memory leak during error handling of some out-of-memory conditions during xml_document::load

Compatibility improvements:
- Fix exported symbols in CMake DLL builds when using CMake
- Fix exported symbols in CMake shared object builds when using -fvisibility=hidden

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-11-07 08:39:05 -08:00
..
2022-08-24 08:26:55 -07:00
2022-10-27 08:55:20 -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>