meta-openembedded/meta-oe
Gyorgy Sarvari ae5a3b889d
uriparser: add ptest support
It takes about a second to execute.

The test suite is covered by a different license (lgpl 2.1+) than the
main recipe (3-clause bsd).

Sample output:

root@qemux86-64:~# ptest-runner
START: ptest-runner
2025-12-22T19:34
BEGIN: /usr/lib/uriparser/ptest
[==========] Running 407 tests from 35 test suites.
[----------] Global test environment set-up.
[----------] 14 tests from CopyUriSuite
PASS:  CopyUriSuite.ErrorSourceUriNull
PASS:  CopyUriSuite.ErrorDestUriNull
[...many lines...]
PASS:  SetUserInfo.UriWithoutHostNonNullRejected
[----------] 2 tests from VersionSuite
PASS:  VersionSuite.EnsureVersionDefinesInSync
PASS:  VersionSuite.EnsureRuntimeVersionAsExpected
[----------] Global test environment tear-down
[==========] 407 tests from 35 test suites ran.
[  PASSED  ] 407 tests.
DURATION: 1
END: /usr/lib/uriparser/ptest
2025-12-22T19:34
STOP: ptest-runner
TOTAL: 1 FAIL: 0

Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-12-22 18:20:58 -08:00
..
classes meta-oe: image: optionally remove RAW image after sparse image creation 2025-09-15 09:55:16 -07:00
conf uriparser: add ptest support 2025-12-22 18:20:58 -08:00
dynamic-layers thingsboard-gateway: upgrade 3.7.4 -> 3.8.0 2025-12-21 08:54:01 -08:00
files
lib/oeqa/selftest/cases
licenses licenses: add licenses for ktx-software 2025-07-22 20:02:18 -07:00
recipes-benchmark fio: ignore CVE-2025-10824 2025-12-16 19:57:32 -08:00
recipes-bsp pointercal: Add HOMEPAGE variable 2025-12-10 08:58:48 -08:00
recipes-connectivity libwebsockets: upgrade 4.3.5 -> 4.5.2 2025-12-16 19:57:32 -08:00
recipes-core dbus-cxx: upgrade 2.5.2 -> 2.6.0 2025-12-21 08:54:05 -08:00
recipes-crypto botan: add ptest support 2025-12-16 19:57:33 -08:00
recipes-dbs postgresql: upgrade 17.6 -> 17.7 2025-12-16 19:57:32 -08:00
recipes-devtools nodejs: remove extra CVE_PRODUCT 2025-12-22 18:20:58 -08:00
recipes-extended fluentbit: upgrade 4.2.0 -> 4.2.1 2025-12-21 23:29:18 -08:00
recipes-gnome gtkmm4: update 2025-12-03 17:39:27 -08:00
recipes-graphics vulkan-cts: upgrade 1.4.4.2 -> 1.4.5.0 2025-12-21 23:29:18 -08:00
recipes-kernel trace-cmd: Add HOMEPAGE variable 2025-12-10 08:58:47 -08:00
recipes-multimedia libopusenc: upgrade 0.2.1 -> 0.3 2025-12-20 11:41:03 -08:00
recipes-navigation Revert "proj: Fix do_package QA issue for unshipped bash-completion files" 2025-12-11 09:32:46 -08:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing cups-filters: patch CVE-2025-64524 2025-12-10 08:56:12 -08:00
recipes-security kernel-hardening-checker: upgrade 0.6.10.2 -> 0.6.17.1 2025-11-11 10:19:41 -08:00
recipes-shells dash: upgrade 0.5.13 -> 0.5.13.1 2025-10-21 20:02:39 -07:00
recipes-support uriparser: add ptest support 2025-12-22 18:20:58 -08:00
recipes-test cunit: inherit sourceforge-releases class 2025-11-12 09:38:58 -08:00
COPYING.MIT
README.md README.md: Change maintainer from Andreas to Khem for gnome, multimedia, xfce 2025-09-19 12:21:59 -07:00
SECURITY.md

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.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

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