Ok, got it thanks.
Indeed wayland is enabled in my distro features, so my question is more: is
there any reason to remove x11 from package config when "wayland" is
enabled as a distro feature (but maybe it is no longer a question to be
addressed ot yocto community)? As Ross mentioned, there can both be built.
On Mon, Sep 23, 2019 at 3:42 PM Jussi Kukkonen <j...@goto.fi> wrote:
>
> On Mon, 23 Sep 2019 at 15:48, Jean-Baptiste MARIE <
> jbaptiste.ma...@gmail.com> wrote:
>
>> PACKAGECONFIG_remove_imxgpu2d = " \
>> ${@bb.utils.contains("DISTRO_FEATURES", "wayland", "x11", "", d)} \
>> "
>>
>
> What Ross said: If wayland is in distro features this will remove the x11
> packageconfig which means disabling the X11 backend for Gdk and removing
> the X11-related API from libgdk3.so (and not installing the gdk-x11-3.0.pc
> file which was the immediate reason for your build failure).
>
> Jussi
>
>
>>
>> CFLAGS_append_imxgpu2d = " \
>> -DLINUX \
>> ${@bb.utils.contains('DISTRO_FEATURES', 'wayland', '-DEGL_API_FB
>> -DEGL_API_WL', '', d)} \
>> "
>>
>> - meta-solidrun-arm-imx6 (branch rocko): that branch overloads gtk recipe
>> with the .bbappend as shown below:
>>
>> DEPENDS_append_imxgpu2d = " virtual/egl"
>>
>> PACKAGECONFIG_remove_imxgpu2d = " \
>> ${@bb.utils.contains("DISTRO_FEATURES", "wayland", "x11", "", d)} \
>> "
>>
>> I do not see any reason why gdk-x11-3.0 would not be built
>>
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
