Files
meta-openembedded/meta-oe
Fabien Parent 2117bbee20 gpsd-machine-conf: allow creation of an empty package
gpsd-machine-conf is an empty recipe that does not ship any files on the
rootfs. This recipe is targeted to be extended by a bbappend that
will provide the gpsd machine configuration.

In the case where gpsd-machine-conf is included into an image, and if no
layers is providing the machine configuration, the build fails with
the following error:

	No match for argument: gpsd-machine-conf
	Error: Unable to find a match: gpsd-machine-conf

This error is because no package was created for gpsd-machine-conf
since the recipe does not install any files.

This commit allows the creation of an empty package in order to avoid
the do_rootfs failure when this package is included into an image.

Signed-off-by: Fabien Parent <fabien.parent@linaro.org>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-06-30 13:39:29 -04:00
..
2022-05-09 08:59:46 -07:00
2022-06-30 13:39:28 -04:00
2022-05-24 08:39:45 -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>