Re: [meta-intel] Why libva-egl1 request x11 in a Wayland configuration (solved)
Le 06/12/2016 à 12:19, Ylinen, Mikko a écrit : You could ave a libva_%.bbappend that adds: RDEPENDS_${PN}-egl_remove = "${@base_contains("DISTRO_FEATURES", "x11", "", "${PN}-x11", d)}" Mikko, thanks for the magic. I guess that a correction in meta-intel would be required. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Why libva-egl1 request x11 in a Wayland configuration
Hi Dominig, On Mon, Dec 5, 2016 at 4:39 PM, Dominig ar Foll (Intel Open Source) < dominig.arf...@fridu.net> wrote: > Jussi, > I suspect something like that as well, but I am surprised that no-one is > facing the same bug. People using Wyaland, QT and trying to build and SDK > should not be new. > > Who would know why that statement has been added ? > How to find a layer that would create a link to libx11 in a complex yocto > built ? > > Looks like it's been like that since it was introduced in meta-intel so it's hard to tell why. That dependency setting does not follow x11 DISTRO_FEATURE but unconditionally sets the dependency to libva-x11 even if it does not exist (which is when x11 DISTRO_FEATURE is not set) You could ave a libva_%.bbappend that adds: RDEPENDS_${PN}-egl_remove = "${@base_contains("DISTRO_FEATURES", "x11", "", "${PN}-x11", d)}" -- Mikko -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Why libva-egl1 request x11 in a Wayland configuration
Le 05/12/2016 à 13:59, Jussi Kukkonen a écrit : On 2 December 2016 at 18:30, Dominig Ar Follwrote: Hello, I am activating libva in AGL distribution which is based on Yocto 2.1 (krogoth). When I look in libva-egl1 I can see that it call for x11 as well as Wayland .But I do not understand why ? I suspect this is incorrect in the recipe: RDEPENDS_${PN}-egl =+ "${PN}-x11" or does something actually link with libx11? Jussi, I suspect something like that as well, but I am surprised that no-one is facing the same bug. People using Wyaland, QT and trying to build and SDK should not be new. Who would know why that statement has been added ? How to find a layer that would create a link to libx11 in a complex yocto built ? Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] Why libva-egl1 request x11 in a Wayland configuration
On 2 December 2016 at 18:30, Dominig Ar Follwrote: > Hello, > > I am activating libva in AGL distribution which is based on Yocto 2.1 > (krogoth). > > Adding in the local.conf the request fro libva, va-instal and > gstreamer-vaapi seems to do the trick for an image. > IMAGE_INSTALL_append += " \ >libva \ >va-intel \ >gstreamer-vaapi-1.0 " > > My issue comes when I try to build the SDK. Then I get the following error: >Computing transaction...warning: Can't install > libva-dev-1.7.0-r0@corei7_64: Can't install > libva-egl1-1.7.0-r0@corei7_64: no package provides libva-x11 > warning: Can't install gstreamer-vaapi-1.0-dev-0.7.0-r0@corei7_64: > unable to install provider for libva-dev: > > When I look in libva-egl1 I can see that it call for x11 as well as > Wayland .But I do not understand why ? > > I suspect this is incorrect in the recipe: RDEPENDS_${PN}-egl =+ "${PN}-x11" or does something actually link with libx11? - Jussi Any hint would be very welcome. > > Dominig > > dominig@dominig-t460:~/AGL/build> rpm -qpR > ./tmp/work/corei7-64-agl-linux/libva/1.7.0-r0/deploy- > rpms/corei7_64/libva-egl1-1.7.0-r0.corei7_64.rpm > attention : ./tmp/work/corei7-64-agl-linux/libva/1.7.0-r0/deploy- > rpms/corei7_64/libva-egl1-1.7.0-r0.corei7_64.rpm: > Entête V4 DSA/SHA1 Signature, clé ID c > da422ed: NOKEY > libffi.so.6()(64bit) > libegl-mesa >= 11.1.1 > libwayland-server.so.0()(64bit) > libwayland-client.so.0()(64bit) > libdrm.so.2()(64bit) > libva.so.1()(64bit) > libEGL.so.1()(64bit) > libdl.so.2()(64bit) > libffi6 >= 3.2.1 > libc.so.6(GLIBC_2.2.5)(64bit) > libva-x11 > libva >= 1.7.0 > wayland >= 1.9.0 > librt.so.1()(64bit) > libgbm1 >= 11.1.1 > libdrm2 >= 2.4.67 > libexpat.so.1()(64bit) > libc6 >= 2.23 > libgbm.so.1()(64bit) > libm.so.6()(64bit) > rtld(GNU_HASH) > libc.so.6()(64bit) > libpthread.so.0()(64bit) > libexpat1 >= 2.1.0 > libffi.so.6()(64bit) > libegl-mesa >= 11.1.1 > libwayland-server.so.0()(64bit) > libwayland-client.so.0()(64bit) > libdrm.so.2()(64bit) > libva.so.1()(64bit) > libEGL.so.1()(64bit) > libdl.so.2()(64bit) > libffi6 >= 3.2.1 > libc.so.6(GLIBC_2.2.5)(64bit) > libva-x11 > libva >= 1.7.0 > wayland >= 1.9.0 > librt.so.1()(64bit) > libgbm1 >= 11.1.1 > libdrm2 >= 2.4.67 > libexpat.so.1()(64bit) > libc6 >= 2.23 > libgbm.so.1()(64bit) > libm.so.6()(64bit) > rtld(GNU_HASH) > libc.so.6()(64bit) > libpthread.so.0()(64bit) > libexpat1 >= 2.1.0 > /bin/sh > dominig@dominig-t460:~/AGL/build> > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > -- > ___ > meta-intel mailing list > meta-intel@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-intel > -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] Why libva-egl1 request x11 in a Wayland configuration
Hello, I am activating libva in AGL distribution which is based on Yocto 2.1 (krogoth). Adding in the local.conf the request fro libva, va-instal and gstreamer-vaapi seems to do the trick for an image. IMAGE_INSTALL_append += " \ libva \ va-intel \ gstreamer-vaapi-1.0 " My issue comes when I try to build the SDK. Then I get the following error: Computing transaction...warning: Can't install libva-dev-1.7.0-r0@corei7_64: Can't install libva-egl1-1.7.0-r0@corei7_64: no package provides libva-x11 warning: Can't install gstreamer-vaapi-1.0-dev-0.7.0-r0@corei7_64: unable to install provider for libva-dev: When I look in libva-egl1 I can see that it call for x11 as well as Wayland .But I do not understand why ? Any hint would be very welcome. Dominig dominig@dominig-t460:~/AGL/build> rpm -qpR ./tmp/work/corei7-64-agl-linux/libva/1.7.0-r0/deploy-rpms/corei7_64/libva-egl1-1.7.0-r0.corei7_64.rpm attention : ./tmp/work/corei7-64-agl-linux/libva/1.7.0-r0/deploy-rpms/corei7_64/libva-egl1-1.7.0-r0.corei7_64.rpm: Entête V4 DSA/SHA1 Signature, clé ID c da422ed: NOKEY libffi.so.6()(64bit) libegl-mesa >= 11.1.1 libwayland-server.so.0()(64bit) libwayland-client.so.0()(64bit) libdrm.so.2()(64bit) libva.so.1()(64bit) libEGL.so.1()(64bit) libdl.so.2()(64bit) libffi6 >= 3.2.1 libc.so.6(GLIBC_2.2.5)(64bit) libva-x11 libva >= 1.7.0 wayland >= 1.9.0 librt.so.1()(64bit) libgbm1 >= 11.1.1 libdrm2 >= 2.4.67 libexpat.so.1()(64bit) libc6 >= 2.23 libgbm.so.1()(64bit) libm.so.6()(64bit) rtld(GNU_HASH) libc.so.6()(64bit) libpthread.so.0()(64bit) libexpat1 >= 2.1.0 libffi.so.6()(64bit) libegl-mesa >= 11.1.1 libwayland-server.so.0()(64bit) libwayland-client.so.0()(64bit) libdrm.so.2()(64bit) libva.so.1()(64bit) libEGL.so.1()(64bit) libdl.so.2()(64bit) libffi6 >= 3.2.1 libc.so.6(GLIBC_2.2.5)(64bit) libva-x11 libva >= 1.7.0 wayland >= 1.9.0 librt.so.1()(64bit) libgbm1 >= 11.1.1 libdrm2 >= 2.4.67 libexpat.so.1()(64bit) libc6 >= 2.23 libgbm.so.1()(64bit) libm.so.6()(64bit) rtld(GNU_HASH) libc.so.6()(64bit) libpthread.so.0()(64bit) libexpat1 >= 2.1.0 /bin/sh dominig@dominig-t460:~/AGL/build> -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel