Add intel-media-driver recipe

[hmaarrfk]

Needed for better hardware acceleration for video stuff:
conda-forge/libva-utils-feedstock#36

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/intel-media-driver/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/intel-media-driver/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

[hmaarrfk]

@wolfv is it normal that when i bulid locall with

rattler-build build

I get an 800MB info file:

[hmaarrfk]

cc: @ehfd for review @traversaro @isuruf

[ehfd]

I see no issues.

[hmaarrfk]

Thanks you two. I'll give isuru some time to chime in (lets say till end of sept) and merge on oct 1st if I don't hear anything from him.

I think this will be useful to get FFMPEG to take more advantage of the hardware, but I haven't really proven that out quite yet.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/intel-media-driver/recipe.yaml, recipes/libvpl/recipe.yaml, recipes/libvpl-tools/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/intel-media-driver/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

For recipes/libvpl/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

For recipes/libvpl-tools/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

[hmaarrfk]

Ok this is looking pretty promissing
conda-forge/ffmpeg-feedstock#279

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/libvpl/recipe.yaml, recipes/libvpl-tools/recipe.yaml, recipes/intel-media-driver/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/libvpl-tools/recipe.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on ${{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/libvpl/recipe.yaml, recipes/intel-media-driver/recipe.yaml, recipes/libvpl-tools/recipe.yaml) and found it was in an excellent condition.