Files
meta-openembedded/meta-oe
Gyorgy Sarvari b58e57f35d libmanette: fix ptests
The original content of the ptest package, manette-test, is a helper demo
application (like evtest), and not a test suite. Also, the recipe did not
provide a run-ptest script.

Fix it by installing the actual tests, and adding a run-ptest script.

Note that the test folder structure looks like a gnome desktop test suite
(and the application is under the gnome umbrella), however the project
doesn't provide all necessary scaffolding for gnome-desktop-test to work, so
the tests are executed directly from the run-ptest script.

Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
2025-10-20 08:53:20 +02:00
..
2025-10-17 10:51:27 +02:00
2025-10-17 10:51:27 +02:00
2025-10-02 15:16:50 +02:00
2025-10-20 08:53:14 +02:00
2025-10-20 08:53:18 +02:00
2025-10-20 08:53:04 +02:00
2025-10-01 19:40:58 +02:00
2025-10-20 08:53:20 +02:00
2025-09-18 11:49:40 +02:00

meta-oe
=======

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: kirkstone 

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][kirkstone]' 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][kirkstone][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: Gyorgy Sarvari <skandigraun@gmail.com>
Layer maintainer emeritus: Armin Kuster <akuster808@gmail.com>