This seems like libepoxy was not properly rebuilt when you changed
DISTRO_FEATURS, even though it should have been. Can you try to reproduce
the issue on master please?
Alex
On Tue, 10 Nov 2020 at 16:14, Adrian Fiergolski <
adrian.fiergol...@fastree3d.com> wrote:
> Hi Alex,
>
> Thank you for
Hi Alex,
Thank you for the hint. It led me to the source of the problem, which
was libepoxy.
It looks that after changing configuration (DISTRO_FEATURES_remove = "
x11"), SSTATE was still populating sysroot of gtk+3 with the older
version of libepoxy configuration file (*.pc) creating dependency
Do you actually need gtk+3 in your image?
There is a poky configuration that builds core-image-weston without x11,
and core-image-weston does pull in gtk+3, and all that happens without
errors:
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json?h=zeus#n638
so I'd
Hi,
I am building an image based on core-image-weston.
I would like to use only wayland backend, thus I defined in my machine's
configuration:
DISTRO_FEATURES_append = " wayland"
DISTRO_FEATURES_remove = " x11"
I have a problem with build of gtk+3:
| checking for pango pangocairo
