meta-openembedded/meta-multimedia
Markus Volk 9294503921 nv-codec-headers: add recipe
These headers are needed to build cuda/nvdec support for ffmpeg but it is
also a build dependency for gnome-remote-desktop where cuda support can't be disabled.

The Makefile has a hardcoded prefix. Instead of patching it and inherit autotools
just install the files manually. On the whole its what the Makefile does and it
looks easier this way.

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2023-01-15 10:53:20 -08:00
..
classes Convert to new override syntax 2021-08-03 10:21:25 -07:00
conf layer.conf: update LAYERSERIES_COMPAT for mickledore 2023-01-04 14:34:04 -08:00
licenses Alliance for Open Media: new library 2020-10-06 08:45:24 -07:00
recipes-connectivity gssdp: check opengl is enabled or not 2022-11-10 10:41:35 -08:00
recipes-dvb Make tvheadend recipe compatible with the latest tvheadend version 2023-01-12 09:02:10 -08:00
recipes-mkv recipes: Update LICENSE variable to use SPDX license identifiers 2022-03-04 17:41:45 -08:00
recipes-multimedia nv-codec-headers: add recipe 2023-01-15 10:53:20 -08:00
recipes-support xdg-desktop-portal-wlr: Add wayland to REQUIRED_DISTRO_FEATURES 2023-01-11 08:37:58 -08:00
COPYING.MIT
README README: update to main repo 2021-09-27 11:34:55 -07:00

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master

URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe
branch: master

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' 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-multimedia][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: Andreas Müller <schnitzeltony@gmail.com>