[meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver

[Tom Zanussi]

On Thu, 2013-03-07 at 14:57 +0200, Laurentiu Palcu wrote:
> On Wed, Mar 06, 2013 at 03:11:19PM -0600, Tom Zanussi wrote:
> > 
> > OK, freedesktop.org is back, but now get this in do_rootfs, for
> > crownbay:
> > 
> > 
> > | Computing transaction...error: Can't install va-intel-1.0-r1 at core2: no
> > package provides libva-egl
> > | 
> > | Saving cache...
> > | 
> > | ERROR: Function failed: do_rootfs
> > (see /usr/local/dev/yocto/nitin-test/build/tmp/work/crownbay-poky-linux/core-image-sato/1.0-r0/temp/log.do_rootfs.3779 for further information)
> > ERROR: Task 7
> > (/usr/local/dev/yocto/nitin-test/meta/recipes-sato/images/core-image-sato.bb, do_rootfs) failed with exit code '1'
> > 
> > poky/master is at:
> > 
> > commit 6663b79452bcdd95fc69e1ec853baae6c5297ab2
> > Author: Andreas Oberritter <obi at opendreambox.org>
> > Date:   Tue Mar 5 18:56:40 2013 +0100
> > 
> >     libpcap: fix description variable
> >  
> > in local.conf:
> > 
> > MACHINE ??= "crownbay"
> > LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16 commercial"
> > 
> > Tom
> > 
> Hmmm, it seems that libva-egl package is not built because, in the new
> version, the check for egl availability is done using pkg-config. And
> the emgd-driver-bin does not provide an egl.pc file...
> 
> There are 4 solutions to this:
>  * make libva use the old method of detecting egl, so it builds libva-egl anyway;
>  * override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately to configure.
>    I tested it and it worked fine adding the following snippet to libva recipe:
> 
> do_configure_prepend () {
> 	export EGL_CFLAGS="-I${STAGING_INCDIR}"
> 	export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
> }
> 
>  * we talk with the egmd maintainers to include *.pc file in the package;
>  * we create the *.pc files ourselves;
> 
> What do you guys think?
> 

I'll leave it up to Nitin since he's the one who's been working with
emgd lately and requested this upgrade, but it seems to me it would be
good to do something we could 'upstream' to the emgd team, so how about
the last option (create the *.pc files ourselves) and send the results
to the emgd maintainers and see if they'd be interested?

Tom

> Thanks,
> Laurentiu